This feature would help anyone with limited bandwidth. (since bandwidth throttling is currently unavailable.) This would allow uses to work without the interruption of a slow network connection.
RealTimeSync should have an option to detect when a mouse or keyboard are in use. With an additional option to restart after a selectable length of time.
For example, if I choose to restart syncing after 1 minute of no activity, syncing would restart after 1 minute, but pause again (or restart the counter) if the user starts to use the mouse/keyboard again.
Hope to see this feature soon.
RealtimeSync Auto Pause Feature Request
- Posts: 1
- Joined: 26 Aug 2015
- Posts: 6
- Joined: 1 Jul 2015
It's a blunt instrument that affects manually run "foreground" FreeFileSync tasks as well as ones automatically run "in background" by RealTimeSync, but would opening FreeFileSync's GlobalSettings.xml file (after temporarily quitting all of your RealTimeSync and FreeFileSync tasks) and changing *RunWithBackgroundPriority Enabled* to *"true"* possibly help? Be warned, though, that it can really slow down how long syncs take to complete.
My own computer has a 7- or 8-year-old Core2 CPU but is hooked up to relatively fast broadband. Leaving FreeFileSync running at normal priority interfered with foreground work (particularly in browsers), but because of CPU, not bandwidth, usage. Using GlobalSettings to enable background priority (which I believe equates to "Low" process priority) slowed down my syncs too much, so I compromised by setting my FreeFileSync and RealTimeSync process priorities to merely "Below Normal" using a third-party utility (System Explorer). That seems to work reasonably well for me. I still experience a slight slowdown in foreground work during the comparison phase of RealTimeSync-triggered FreeFileSync runs, but it's tolerable, and my syncs complete in a reasonable amount of time.
Caveat: I've only used FreeFileSync/RealTimeSync for transfers to local drives, USB drives, and LAN drives, never over the Internet, so I don't have first-hand experience with how slowing down FFS priority might affect those transfers, if at all.
My own computer has a 7- or 8-year-old Core2 CPU but is hooked up to relatively fast broadband. Leaving FreeFileSync running at normal priority interfered with foreground work (particularly in browsers), but because of CPU, not bandwidth, usage. Using GlobalSettings to enable background priority (which I believe equates to "Low" process priority) slowed down my syncs too much, so I compromised by setting my FreeFileSync and RealTimeSync process priorities to merely "Below Normal" using a third-party utility (System Explorer). That seems to work reasonably well for me. I still experience a slight slowdown in foreground work during the comparison phase of RealTimeSync-triggered FreeFileSync runs, but it's tolerable, and my syncs complete in a reasonable amount of time.
Caveat: I've only used FreeFileSync/RealTimeSync for transfers to local drives, USB drives, and LAN drives, never over the Internet, so I don't have first-hand experience with how slowing down FFS priority might affect those transfers, if at all.
