Below is all tested on this version https://beta.rclone.org/branch/v1.51.0-326-g791f879a-fix-check-first-beta/
Disk utilization is really low (below 10%) according to Task manager.
Besides thanks to running it so often most of the data is cached anyways so disk access should be almost non-existent.
Finally the latest changes were synced. Now i could finally test "dry-run" against "non-dry-run without changes". So i have three situations
- --dry-run: 2-3 minutes
- Normal run where transfers are encountered: depending on how soon the transfers are found checking can take anywhere from 9 to 25 minutes
- Normal run where no transfers are found: 2-3 minutes
So there is no difference between the dry-run and a normal run where nothing needs to be transferred.
But now the kicker. Tested your new version. It fixes all issues. I don't even have to use the --check-first flag. So copied it to my Rclone production directory and my issue was back.
So WTF... So i went on a testing binge
- Cleared Compatibility assistant. That automatic thing can really $%^$% you over
- Checked priorities of the process and see if that made a difference. Windows Task Scheduler runs tasks at Below Normal priority while running a batch file manually runs it at normal priority
Neither fixed the difference between the way production and test work.
So checked the differences between the test environment and production environment.
- They were testing the same local production data to the same production destination
- The versions were now the same so no difference either.
- Rclone configuration file used is also the same
- The OS and hardware are the same. Well its the same system not 2 different systems so yeah this is obvious
- Compatibility assistant was cleared so no possible side effects there.
- The only difference was the loglevel parameter and the filename where the log was written to. DEBUG for test environment and INFO for production environment
DEBUG log level works perfectly and fast on 1.51 and 1.51.0-326-g791f879a-fix-check-first-beta.
INFO log level has the issue we are discussing here
NOTICE shares INFO's issue
So my question is. Why are INFO and NOTICE log levels not working at full speed while DEBUG is?
I would have thought DEBUG would have affected performance more then NOTICE and INFO. So really surprised about this result.
I also tested the --check-first flag. It fixes the problem as well