Batch job takes much longer than GUI
- Posts: 3
- Joined: 10 Dec 2014
I am testing FreeFileSync as a replacement for a couple of xxcopy-scripts we are running every night. Updating some large network drives (total of 10 TB) takes xxcopy about 15 hours, FFS does it in 3 hours when running in the GUI. Impressive. But, when running this same FFS-job as a batch file, it takes 30 hours. This is unexpected. Anyone any ideas?
-
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
> This is unexpected
Indeed. Both GUI and batch job share the very same sync routines. Rather than being related to FFS it's more likely something else changed between these two runs.
Indeed. Both GUI and batch job share the very same sync routines. Rather than being related to FFS it's more likely something else changed between these two runs.
- Posts: 3
- Joined: 10 Dec 2014
Well, I have been able to reproduce this twice, and as far as I know nothing changed, at least not in the FFS job settings. I have the impression that it is the comparison phase which is taking so long when running the batch job. It is difficult to track batch job progress in real-time, because the log file is completely locked during the run. I look at disk activity in performance monitor.
- Posts: 3
- Joined: 10 Dec 2014
Apparently, the problem was caused by the fact that a scheduled tasks is started with below-standard priority as default.
- Posts: 2
- Joined: 22 Sep 2013
I've had this problem for a while as well (I'm led to believe that Koen might be right about it being a Task Scheduler problem as I also use that).
With the GUI I can complete each of my tasks in 3-5 minutes. Using a batch file (triggered by Task Scheduler) it takes 10 minutes per task at the least (but more typically it takes between 15 and 20 minutes).
The Comparison process seems to be what causes most of the added time (just like Koen said). The time it takes to do the Synchronize process is similar for both the GUI and the batch process (it might take slightly longer with the batch process, but it seems negligible).
For example...
GUI: 3 minutes comparing, 2 minutes synchronizing.
Batch: 10 minutes comparing, 2 minutes synchronizing.
I found a Server Fault topic similar to this, I'll try testing in a few days to see if the answer is applicable to our situation: http://serverfault.com/questions/151824/process-runs-slower-as-a-scheduled-task-than-it-does-interactively
With the GUI I can complete each of my tasks in 3-5 minutes. Using a batch file (triggered by Task Scheduler) it takes 10 minutes per task at the least (but more typically it takes between 15 and 20 minutes).
The Comparison process seems to be what causes most of the added time (just like Koen said). The time it takes to do the Synchronize process is similar for both the GUI and the batch process (it might take slightly longer with the batch process, but it seems negligible).
For example...
GUI: 3 minutes comparing, 2 minutes synchronizing.
Batch: 10 minutes comparing, 2 minutes synchronizing.
I found a Server Fault topic similar to this, I'll try testing in a few days to see if the answer is applicable to our situation: http://serverfault.com/questions/151824/process-runs-slower-as-a-scheduled-task-than-it-does-interactively
