Uploads are taking over 10 seconds which I'm sure is much longer than I've been accustomed to.
I thought it was down to the large number of 'recent sketches' in preferences.txt (180!) but no. (It's now 8, but no change.)
I switched ports, and tried my Nano instead of the UNO, but still the same duration. Nothing looks wrong in Device Manager. No errors are reported during the upload.
I restarted my Win 10 PC, but no change.
The 10 s is how long it takes for the rapid flashing to end. There's then a couple of seconds for operation to actually begin (e.g. Blink).
This is IDE version 1.8.19.
Am I correct in assuming this is abnormally long an upload time? If so, how should I proceed please?
Is this the first upload after you rebooted the PC or consecutive uploads of the same sketch?
Running on a 2nd generation I3 with 8GB RAM and Windows 10, it took approximately 10 seconds to compile blink the first time and 6 seconds for the upload. For consecutive compile/uploads of the same sketch, the full process takes approx. 5 seconds. Target was an Nano with old bootloader; IDE 1.8.19 with verbose output during compilation and during upload enabled.
From that it sounds that your 10 seconds for a pure upload is a tad long but personally I would not call it "abnormally".
Apart from the very first run this morning (when it took about 15 s), Blink is consistently taking about 10 s between Ctrl+U and the first LED flash.
Win 10, i7 4.0 GHz, 32 GB.
After lunch I'll see if reducing the size of my SKETCHES folder
C:\Users\terry\Dropbox\Electronics\Arduino\SKETCHES
is a factor.
Possibly, although that’s a local folder. I’ll temporarily move it.
When you get a chance I’d be interested to know your equivalent
timing please.
BTW, in the brief time that I had IDE 2.0 installed, I’m pretty sure its upload time was noticeably faster. That, and the ease of switching themes tempted me, but I wasn’t comfortable with the radically different layout.
From Ctrl+U to first blink takes about 14 seconds the first time that I do it after starting the IDE and about 12 seconds the second and subsequent times
IDE 2.01 is significantly faster taking about 7 seconds the first time and about 5 seconds subsequently, but none of my timings are very exact
The PC has an AMD Ryzen 7 4800H processor and 16Gb of RAM. It has only one disk drive and that is an SSD, but it is nothing to write home about
Is that the first flash of the upload or the first flash of blink?
If you enable verbose output during upload and disable verbose output during compilation in the IDE (file -> preferences) and you perform an upload, you will see something like below (and a lot more)
Sketch uses 924 bytes (3%) of program storage space. Maximum is 30720 bytes.
Global variables use 9 bytes (0%) of dynamic memory, leaving 2039 bytes for local variables. Maximum is 2048 bytes.
C:\Users\sterretje\Downloads\arduino\arduino-1.8.19-windows\arduino-1.8.19-AVRonly\hardware\tools\avr/bin/avrdude -CC:\Users\sterretje\Downloads\arduino\arduino-1.8.19-windows\arduino-1.8.19-AVRonly\hardware\tools\avr/etc/avrdude.conf -v -patmega328p -carduino -PCOM31 -b57600 -D -Uflash:w:C:\Users\sterretje\AppData\Local\Temp\arduino_build_537712/Blink.ino.hex:i
That last line in above is the upload command that is executed by the IDE (in this case a Nano with old bootloader). You can copy that output (from your system) and paste it in a command prompt. If the ino.hex lives in the usual place (Temp) directory, the upload should be fast from the command line.
That way you can figure out if the upload process is the culprit or the compile process.
You can also check how long the actual compile take fromstarting the compile till the IDE reports the memory usage; you can disable the verbose output for that.
Note:
I'm using a portable install of 1.8.19 for this.
To be clear, my timings were to the first real LED flash caused by the sketch, not the flashes caused by the upload. As noted, the timings were not very exact
The latter. IOW, the point when I would regard uploading finished.
Further info after more tests:
Culling \libraries or its parent folder \SKETCHES did not make uploading noticeably faster. Nor did temporarily moving \SKETCHES out of Dropbox. (Pleased about that because I would not have been prepared to do so, given the main advantage of access from my iPad.)
Then tried 2.0,1 on which uploading was much faster. However other issues with that version prompted further digression.
As @UKHeliBob seems to get similar times maybe I was mistaken about previous performance.
Edit: Verification (Ctrl + R) seems as fast as usual.