This system is mostly in sync already - the folders which are currently Scanning are Send Only - yet I’m seeing 11GB RAM usage (actually 5.6GB in the NAS’s monitoring).
I’ve already turned off Cache Ignored Files - any other clues as to why the RAM usage is so high?
I’ve extracted a heap profile from the Support Bundle:
Part of it is due to the scan progress indication. That means all files that will be scanned are buffered before they are hashed, such that a compeletion percentage can be calculated. This accounts for ~2.3GB according to the profile. You can disable it by setting scanProgressIntervalS to -1.
Another ~2GB is due to joining filepaths while walking the filesystem, which I can’t make any sense of. I mean sure, it’s apparently a lot of files that need to be walked, i.e. a lot of strings to be allocated, but that happens sequentially, so why the buildup.