I’m using SyncTrazor version 1.0.16 with Syncthing version 0.11.2 (should be the latest) on a Windows 7 Pro x64 machine. I’ve been using it for quite a while now to synchronize several hundred GB of files between my two computers.
Even though I marked “run syncthing as a low priority process” in SyncTrazor’s syncthing settings, and even though the program has long finished scanning my drive for the first time, it keeps using a lot of I/O, as well as a lot of RAM. It’s memory usage is comparable to that of Firefox with several open tabs, as can be seen below. These cause my machine to be noticeably less responsive whenever syncthing is working.
How could it’s RAM and disk usage be reduced?
PS I set Rescan Interval=600s on all synced directories.
I had that issue with SyncTrazor as well. Because it was on my wife’s computer, I couldn’t spend time troubleshooting, but installing syncthing-gtk and using the ‘low’ priority option seemed to make it usable again for a ~260Gb folder.
Thank you all for your responses. I’ve closed SyncTrazor and executed syncthing.exe as @canton7 suggested. After completing it’s initial directory scan, the program reported RAM Utilization to be 372 MiB (!), having low CPU & I/O as expected. Process explorer reports similar figures.
Why does syncthing keep using so much RAM? Is there anything I could do to help analyzing this problem? e.g., uploading syncthing logs for the community to review?
Are you looking at what Syncthing reports itself, the “Working set” column in your screenshot, or something else? There’s a million different ways to measure “memory usage”, and most of them are not relevant.
I’m looking at all of them, and they’re all pretty similar. syncthing.exe consumes 297 MiB per it’s own report, 380 MB of “private bytes” and 317 MB of “working set” (as per process explorer), after over an hour of (nearly idle) uptime.
(For comparison, my syncthings idle at around 80 MB with ~520 GB in 150k files being synced. Loading the GUI brings it up to 130 MB. Leaving it alone for 5-10 minutes takes it down again, when Go’s garbage collector + scavenger has run.)
I’m syncing about 500GB in about 157k files, very similar to @calmh. They’re divided between 5 synchronized directories.
I’ve done this again, just to clarify:
I verified that SyncTrazor is down.
Launched syncthing.exe from command line, and closed the browser window it opens.
After about half an hour (synthing long being idle), the program itself reports 295 to 323 MiB under “RAM Utilization”, while process explorer reports numbers between 300 MB to over 400 MB, depending on the exact time and column you’re looking at.
How much memory should syncthing be consuming? How could one calculate it, given the directory & files count & sizes?
Well, the machine I’m using is a laptop with Intel i5-2410M, 4 GB of RAM, Windows 7 x64. @chucic, does that make the figures I mentioned earlier seem reasonable from your perspective?
From the perspective of a user relatively new to syncthing, I think that it’s a great software. But one might expect a software that’s supposed to “sit in the background and do nothing” (when there’s nothing to sync) to require a little less resources in it’s idle time.