I wrote this up which may help:
Know that Windows, in general, has slower file I/O compared to Linux. There are a bunch of places in the PhotoStructure code base where I had to extend default timeouts for Windows or Raspberry Pi. RPi CPUs are 4-10x slower than (even 8-year-old) laptop or desktop CPUs. It’s a huge hit.
This can be “fixed” somewhat by excluding certain directories from your anti-virus software, but that’s not a great solution, and feels a bit unsafe as a general recommendation.
I’d use Docker or an Ubuntu VM running PhotoStructure for Node: you’ll get much more performance out of your current hardware.
Using PhotoStructure for Node means it’s much more convenient to add or remove drives (if you’re doing a big sweep through, say, boxes of old hard drives): just plug in new drives, leave PhotoStructure on “automatic” scanning, and it’ll find new drives and scan them as they’re plugged in.
Here’s the setting:
v2.0-beta.1 is known to accidentally drop remote libraries on Docker: I do not recommend running that build on Docker, unless you explicitly set PS_FORCE_LOCAL_DB_REPLICA=false.
To avoid those kind of issues in the future, I bit the bullet and added Alpine to PhotoStructure’s continuous integration suite a couple weeks ago, and have been working through the issues that popped up in volume and system parsing. I’m much more confident that regressions like in v2.0-beta.1 will be avoided in the future (or at least prior regressions: no telling what new bugs are in store, but that’s why there are alpha and beta builds!)
I’ll push the alpha build of v2.1 as soon as I can: @aneagoe , apologies that v1.1 isn’t working for you on Docker!