PhotoStructure’s sync process should wake up periodically, see what scan paths haven’t been visited for a while, and restart a sync for each of those paths.
This is controlled by the syncIntervalHours setting, which defaults to 24 hours. This topic was brought up a while back, too.
This had been handled by a main when sync got periodically restarted, but if sync is long-lived, I just realized I needed to add an additional “kick” to make sure daily scans happen when they should. This will be added in the next build.
Great, thanks! I missed finding that setting in my search, ta for the link.
I wonder if it would be useful to be able to do a sync just for a folder, kind of like a “Resync this asset” but for a folder and sub-folders. For example, 95% of my library changes will be under the “2021” folder this year, no need to resync folders going back to 1980 as often.
But making this “just work” would be much nicer. I’d thought of adding a “quick sync” option that visits the last N grandparent folders that new assets have been found in.
Unfortunately this didn’t work. I did the following:
10pm Thurs added new photos to library (from Dec-2020 through to Apr-2021)
8am next morning Friday, no new photos showing
1pm Friday shutdown PS, changed syncIntervalHours to 10, started PS back up.
11pm Friday, no new photos showing.
9am Saturday, no new photos. Click “Restart sync”. All new photos show up correctly within 5 minutes.
So to me that says the periodic sync isn’t working (neither the 24 hour default, nor my reduced 10 hour setting). The workaround is okay, clicking Restart sync.
Did I change it in the right place? Why isn’t the 24 hour sync working?
Right. Sorry, I wasn’t very clear in the prior reply: thanks to your prior description of the problem, I looked at that section of code again, and found the bug:
This will be fixed in beta.4 (and then if you can run that test again, that’d be splendid).
To add to this, this doesn’t really make much sense as a default on the windows version (or any non-server based version). I’ve added photos throughout a month, but they still haven’t been picked up.
I typically only use my PC with photostructure in the evenings for 4 hours.
I’ve also attempted removing and re-adding the folder, but no change.
Today, I just updated to beta 4.
Photostrucutre is doing… something. It’s write rate is ~100 MB/s in 5 sec bursts, but there’s no indication on the UI.
However, no new media has shown up.
I’m a huge fan of having an import folder that brings in new media, and then optionally deletes it.
I’m also getting the same thing, but not spikes, more like 200MB/sec consistently. A little worried it’s destroying my SSD. This is how my SSD has been looking since yesterday when I upgraded:
OK, I think there were actually 2 issues going on:
Database VACUUM and OPTIMIZE pragmas weren’t being called properly, which may have led to your large write-ahead-log file
Filesystem root tags were having asset recounts every 5 seconds which was unnecessary. The next beta only rebuilds the filesystem roots when new mountpoints are seen.
sync or sync-file may be crashing for some reason and getting automatically restarted. Restarting requires re-reading the library db which is a bunch of disk I/O. If you send me logs (or if you want to check yourself), we can see if there are any JavaScript heap out of memory or similar ilk.