Compile Speed - testing & feedback needed!

Without more info, I can't know why it's recompiling everything.

If you're willing to try more, here's a few suggestions.

1: Can you post the verbose messages. On 1.0-beta4, enable in the preferences. On 0022, hold the shift key. The speedup only applies to "upload", not "verify".

2: Can you post your boards.txt file? There's several boards in the file, so make sure you're added this line for the board you're using.

3: Can you tell me which operating system and which board you're using? I have most combinations here. While it should work on all, I've only tested a small set of all the possible permutations (eg, only Uno and Teensy 2.0 on Windows, etc)

4: Could you reinstall Teensyduino 0.98? If you have 0.97 or earlier, there was a bug parsing the dependency files. It turns out the Windows and Mac versions have extra white space which isn't present on the Linux version.

Oh that would do it! Yeah I was only doing the compile / shift compile. With upload you're right it works great! Will post to your ticket with my results.

Oppps, guess I could have mentioned it only speeds up "upload" :wink:

I actually spent a lot of time editing that video down to only 2.5 minutes. Maybe I cut too much?

Glad it's working. Hopefully anyone else who tries it will see this and know to use Upload instead of Verify.

I thought the video was very professional actually! Arduino videos are synonymous for me with "Ummm hey guys, this ummm an arduino" with the video being taken by a cellphone camera shakily shooting a monitor you can't read. Your video a welcome surprise-- brief, to the point, informative, and clear.

One of my projects is around 60 files and this is so nice to be able to compile it much faster. If I can ever get git to clone to my machine, I'd love to add an option to skip the verify step of the avrdude upload and get my 30KB compile + upload down to 15s total!

Another important thing for others to note: When you hit "Save" in the Arduino IDE, it cleans the build directory and removes all the pre-compiled files. This also prevents this optimization from being used.

So this would only speed up the part until the size of the module is displayed - right?

Yup, it only speeds up the compile part.

If you're using Teensy, the data transfer goes pretty fast, since it's full USB speed. I recently discovered that Teensy can go even faster. It turns out much of the time is wasted waiting for operating system scheduling. I'm planning to overhaul the process to use overlapping async I/O to remove the dependency on operating system scheduling. I like things to go fast!

The process for official Arduino boards isn't under my control. In fact, with Teensyduino, I try very hard to make sure I don't accidentally alter anything about how non-Teensy boards work. That's why you need to copy that line into boards.txt to enable this.

As a final followup, I prepared a patch and posted it to issue 638.

http://code.google.com/p/arduino/issues/detail?id=638

Due to the underwhelming response, I'm not planning to work further to contribute this feature to the larger Arduino community. The source is there if anyone wants to use it, or continue to improve it and advocate its use.

I gave it a try___ and it worked out for me... Thank you very much, I was so tired of the long building times.
In my case, building time (without upload) was reduced from 15 sec to 5 sec, if I only make a few changes in code, e.g. adjust some timings.

Now I will get Optiboot to speed up the upload, and voila, i will get the max out of my development time...

Thanky.... :wink:

Paul,
Maybe with the release of Leonardo & ATMege324U4 with built in USB, this will come in handy as a tool.
I didn' really notice long compile times before, guess I am not writing long enough programs.

Robert

Yes, the upload to Arduino is slow due to the limited serial speed. It's hard to notice how long the compile takes, because the slow upload takes much longer.

I developed this compile speedup for Teensyduino, which uses the 32u4 chip (and has been Arduino compatible for nearly 2 years). If you've never tried a Teensy, you'll probably be surprised how fast uploading code is. With Teensy's fast data transfer speed, recompiling everything became most of the wait, but this change eliminates most of that wait too.

Here's a video I recently uploaded. Check out the upload speed. It's at approx 0:42 in the video.

Did you actually try this speedup? How much speedup difference does it make on your computer?

I have not tried it. However, I am putting together a Duemilanove type board with the ATMega32U4, and I'm thinking the Teensyduino code could be good on that.

I haven't decided what to do with the extra 6 pins yet; I have going to a jumper block to allow I2C or A4/A5 to connect to the header, and put some parts in support the PE2 & PE6 pins. That leaves PC6 & PC7 still unconnected.

I have assigned the connections to the headers to maintain compatibility, this makes the layout work ok, not sure if the assignments make sense or how much pins_arduino.c will need to be revised.

How does the installer work? Is it version independent, or only applicable to 0022?

I'm hoping that Arduino will eventually go to a make-based compilation, even if the default behavior is to recompile everything.

I have done everything I possibly can to get this improvement into the official Arduino, even to the point of making a video demonstration to solicit more beta testing, since the Arduino Team believed this feature might be too risky without more testing.

My basic feeling is it's nearly impossible to contribute anything to Arduino, other than specific bug fixes. Even "patches welcome" doesn't mean contributed code will actually be used. For example:

http://code.google.com/p/arduino/issues/detail?id=550

Here's another example, where a feature was requested (by the Arduino Team), and I went to the trouble to produce a patch, and screenshots. They didn't like the syntax I chose, but indicated the feature itself was good. So after some back-and-forth to clarify what syntax would be desired, I pretty much redesigned the entire thing and submitted a second patch. It has sat unused for 1 YEAR.

http://code.google.com/p/arduino/issues/detail?id=257

I'm particularly bitter about the very substantial work I put into that redesign. The original approach tried to limit the scope of changes within Arduino. Since they haven't used it, I'm left with a larger patch set which I maintain separately for Teensyduino. Never again will I rework a patch like that.

I'm hoping that Arduino will eventually go to a make-based compilation, even if the default behavior is to recompile everything.

Bill, you know a make-based build has been brought up over and over on the developer mail list. The idea has been consistently rejected.

Given how hard it is to get any patch accepted (other than specific fixes to accepted bugs), even in cases like these where the idea was approved, even when "patches welcome" is said, obviously there's zero chance Arduino will ever use make, even if someone is foolish enough to try contributing that code.

The Teensyduino installer is my kludge to avoid completely forking Arduino. In hindsight, forking would be easier. My installer is NOT version independent. With each new Arduino version, it needs to be updated. It only works well because I put a huge amount of work into ongoing maintenance. I'm a little crazy like that....

I keep hoping Arduino will be more open. In hindsight, I regret putting so much work into sharing this compile speedup. I've easily spent 10X more time trying to get Arduino to actually use it than I did writing it in the first place!

There's "wiring" ...
I've been wondering whether they've been collecting frustrated IDE developers...

This is making me happy that I have 3 teensy's rather a arduino, besides this modification there is so many other things that specifically make a teensy great... I'm really surprised to see so many people buying a arduino and trying to use it as a g-code interpreter for a cnc. Teensy' 2+ offers so much more program space and communication speed...

I'd like to thank paul for supporting open source. I've seen several attempts of him trying to contribute to different projects.
if arduino doesnt resolve this issue, i'd still like to say your hard work has been appreciated by at least 2 of your customers. if only the whole community could enjoy your fixes without such a long delay from the arduino team.

Maybe now that Arduino 1.0 is finally released, hopefully they'll have more time to look at "post-1.0" contributions like this speedup?

That's my hope.

Sorry, Paul, I know it's frustrating to submit patches that languish. I just haven't had time to properly handle everything. That was one of the reasons I wanted to get the 1.0 release out - so that I could go back and start integrating more of the patches and changes that have been accumulated. I'll do my best to get them sorted soon.

Certainly there are much more urgent things than compile speedup. Issue 527, for example.

It definitely is frustrating to see patches go unused. I would contribute a LOT more if my existing patches were used, and Arduino in general had an openness towards contributions that was reflected in the actual usage of patches people submit. I'm imagine quite a few other people, some of whom I know have utterly given up on contributing to Arduino.

On unused patches, I'd like to remind you about the one I submitted on issue 550. You wrote "patches welcome" in October. I submitted the patch 2 days later, and an improved patch after another 3 days (based on some user feedback from the first). It has now sat for a full month. Will it ever get used?

Especially when you say "patches welcome", but then you don't use them, that is really disheartening to contributors.

Another perfect example is "menu cleanup" (issue 257), which has sat unused for over 1 year! I never expected my original patch to be used. But then in November (1 year ago) you specifically asked me to completely rework the boards.txt syntax. I did, and submitted a completely new patch within a week. It was a substantial amount of work. Why would you ask me to do all that work, but then never use it?

Still, I have at least a few more patches heading your way soon. They're all little things recently discussed on the developer mail list. I'm reluctant to submit any more "big" patches.

On the original topic (with no intent to discount the patches discussion):

I've been using teensy .99 for the "compile only what's needed" feature and it's been working wonderfully, with no issues, to reduce my debug turn-around times. Thank you for the effort you put into it.

Glad to hear it's working and helping you. :slight_smile: