RealTimeSync seems to slow down the computer

[Salvatore Besso]

hello again,

I have started to play with RTS following the instructions found in the documentation and all seems to work well. On this computer (from which I'm writing) I have eight jobs that were normally executed manually every now and then. I have saved them as batch and then loaded in RTS and saved as ffs_real files. Then I have copied the eight ffs_real files in shell:startup.

All good? Nearly.

The eight job icons are visible in the system tray and all the jobs run well as soon as changes in the synced folders are detected by the operating system.

Nevertheless I have noticed an overall slow down in the response of the computer, even with an as simple operation as opening MyComputer to browse folders.

But more evidence popped out when I tried to launch another program. This is the time needed by the other program to complete loading and to see its window on the screen:

Without any RTS job running: 2 seconds
With the eight RTS jobs running: almost one minute

But notice that the other program requires almost one minute to start even if none of the RTS jobs has something to do. What is RTS doing when it is totally idle, that's to say, when it's waiting for change notifications from the OS? Moreover, the other program is not involved in any way with any of the RTS jobs. This puzzles me down.

Can you help me? For now I have removed the RTS jobs from the startup folder.

Some information on hardware and software:

• CPU: Core 2 Quad Q9550 at 2.83 GHz.
• RAM: 8 GB
• Disks: SSD with plenty of space on them
• Windows 10 Pro x64 22H2 with latest updates
• FFS and RTS latest Donation Edition

If you need more information, I can try again looking what's happening in the task manager.

Salvatore

[therube]

With the eight RTS jobs running: almost one minute

And with only 1 running?

the other program requires almost one minute to start even if none of the RTS jobs has something to do

That is with 8 running, but nothing to do?



Do any of your RTS overlap in the directories they are monitoring?


(On my end, I run one RTS on an ancient XP system without issue.)

[Salvatore Besso]

And with only 1 running?

I'm trying just now. Will report.

That is with 8 running, but nothing to do?

Exactly. Nothing to do for the eight jobs, but the other program still requires almost one minute to start instead of two seconds.

Do any of your RTS overlap in the directories they are monitoring?

Absolutely not.

(On my end, I run one RTS on an ancient XP system without issue.)

Ok, here are the freshly made tests to measure load time of the other application I waited for the jobs to stay idle before measuring:

No RTS job running: 2.5 seconds

1 RTS job running idle: 7.5 seconds
2 RTS job running idle: 10 seconds
3 RTS job running idle: 13 seconds
4 RTS job running idle: 17.5 seconds
5 RTS job running idle: 22 seconds
6 RTS job running idle: 23 seconds
7 RTS job running idle: 27 seconds
8 RTS job running idle: 30 seconds

What I see in the task manager:

Task manager.jpg (106.22 KiB) Viewed 1295 times

Ok, I admit that things are a bit better than before, when I had a QNAP NAS as destination. I have dismissed it due to some access problems that support was not able to resolve without introducing some intricacies. So I have bought a Synology DX517 extension for my existing Synology DS918+ NAS. The access problem has gone for good.

Anyway the 48 seconds that I had with the QNAP are now 30 seconds with the Synology, and the jobs have almost nothing to do, not considering a very small sporadic disk activity of 0.1 MB/s and an equally very small sporadic network activity of 0.1 Mbps, both noth visible in the screenshot, but they are there. This doesn't seem normal to me.

BTW, why I see sixteen tasks instead of eight?

Salvatore

[xCSxXenon]

The issue obviously revolves around the monitoring of those remote folders. Are they monitoring UNC paths or do you have these locations mapped as drive letters?

The 16 entries is because both FFS and RTS have a xxx.exe that determines if you need to run xxx32.exe or xxx64.exe. It leaves the main exe running for some reason

[Salvatore Besso]

The issue obviously revolves around the monitoring of those remote folders. Are they monitoring UNC paths or do you have these locations mapped as drive letters?

The 16 entries is because both FFS and RTS have a xxx.exe that determines if you need to run xxx32.exe or xxx64.exe. It leaves the main exe running for some reason

no mapped drives, only UNC paths. These are the eight jobs:

Eight jobs.jpg (87.77 KiB) Viewed 1285 times

Sources on the left are all local folders.

Salvatore

[Salvatore Besso]

The 16 entries is because both FFS and RTS have a xxx.exe that determines if you need to run xxx32.exe or xxx64.exe. It leaves the main exe running for some reason

so I should see a x64 process, and not a 32 bit one, my machine is 64 bit.

If it leaves the main exe running, is it something that should be corrected?

Thank you for the help.

Salvatore

[xCSxXenon]

The 16 entries is because both FFS and RTS have a xxx.exe that determines if you need to run xxx32.exe or xxx64.exe. It leaves the main exe running for some reason

so I should see a x64 process, and not a 32 bit one, my machine is 64 bit.

If it leaves the main exe running, is it something that should be corrected?

Thank you for the help.

Salvatore

There's more to it than just running a 64-bit OS. It is using RTS_x64.exe for me. Are you sure you installed it in "Program Files" and not "Program Files (x86)"?

[xCSxXenon]

Nevermind!
"RealTimeSync - Automated Synchronization" is the entry for RTS_x64.exe
"RealTimeSync - Automated Synchronization (32 bit)" is the entry for RTS.exe, which has to be 32 bit or course

[Salvatore Besso]

There's more to it than just running a 64-bit OS. It is using RTS_x64.exe for me. Are you sure you installed it in "Program Files" and not "Program Files (x86)"?

of course.

Salvatore

[Salvatore Besso]

Nevermind!
"RealTimeSync - Automated Synchronization" is the entry for RTS_x64.exe
"RealTimeSync - Automated Synchronization (32 bit)" is the entry for RTS.exe, which has to be 32 bit or course

but why are they both executed?

Salvatore

[Salvatore Besso]

another update:

In the other thread

"Could not read attributes of file: Temporary access error: ERROR_FILE_NOT_FOUND"

I wrote that I have uninstalled the donation edition and that I have installed the free edition. Running the same eight jobs with the free edition doesn't change the loading time of the program of which I wrote of: always 30 seconds with eight jobs idle.

Salvatore

[Zenju]

I wrote that I have uninstalled the donation edition and that I have installed the free edition. Running the same eight jobs with the free edition doesn't change the loading time of the program of which I wrote of: always 30 seconds with eight jobs idle.

This suggests the slow down is not caused by RealTimeSync, but by FreeFileSync. Perhaps you've set up eight RTS instances, each of which trigger the same FreeFileSync batch job shown on this screenshot: viewtopic.php?t=10209#p38033
Perhaps, FreeFileSync is running all the time due to changes on the network share, and thous causing an overall slow down.

[Salvatore Besso]

hello,

This suggests the slow down is not caused by RealTimeSync, but by FreeFileSync. Perhaps you've set up eight RTS instances, each of which trigger the same FreeFileSync batch job shown on this screenshot: viewtopic.php?t=10209#p38033
Perhaps, FreeFileSync is running all the time due to changes on the network share, and thous causing an overall slow down.

yes, eight RTS instances each one triggering one different batch, not eight RTS instances all triggering the same batch! The screenshot shows eight jobs, corresponding to eight different ffs_batch and eight different ffs_real.

RTS instances.jpg (8.29 KiB) Viewed 1212 times

The overall slow down, as I reported in a previous reply, already appears with only one job running, incrementing as other jobs are executed.

Salvatore

[Salvatore Besso]

hello,

any news about this issue? I had to temporarily dismiss the real time sync feature opting for a scheduled task than runs a batch containing the eight jobs every ten minutes.

Salvatore