Version 1.0.0-beta.1 is out!

Const · May 6, 2021, 5:50pm

Node on Ubuntu 20 also complains on lack of Node.js:

~/photostructure-for-servers$ ./start.sh

Please install Node.js v14.16.0 or later
Please refer to https://photostructure.com/server/photostructure-for-node/.
You can also visit https://forum.photostructure.com for help.

but

$ node --version
v14.16.0

so, “new” start command works…

./photostructure

mrm · May 6, 2021, 5:58pm

Thanks for reporting this! I believe I’ve fixed this, and will be releasing beta.2 as soon as the other tests pass.

mrm · May 6, 2021, 6:03pm

Yarn is a package manager for Node.js.

PhotoStructure uses it instead of the default package manager, npm, for a litany of reasons, including speed, repeatability, and because npm install provides no way to silence a bunch of compilation warnings in dependencies and a bunch of other console spam.

@Daniel is actually one of Yarn’s contributors

harrisc · May 7, 2021, 8:00am

I am running version 1.0.0-beta.1 on a Windows 10 PC i&-6700 with 16 GB RAM. There are 107,902 assets,
212,839 image files, 2,220 video files and 5,071 tags.The rebuild will take 2 to 3 days. FYI according to task manager CPU usage sits at about 60%, Memory at about 70% and Disk at about 60%.

Is there anything that can be done to enable the program to use more resources so that any rebuild would take a shorter time?

mrm · May 7, 2021, 11:38am

Yes!

github.com

photostructure/photostructure-for-servers/blob/aaa0caf6479dcadbbdd06c9c2c3db21e2f4965ec/defaults.env#L305


      
          
          # +––––––––––––––––––+
          # |  cpuLoadPercent  |
          # +––––––––––––––––––+
          #
          # PhotoStructure runs many things in parallel during library synchronization.
          # The maximum number of concurrent file imports that PhotoStructure will
          # schedule at a time will be the number of CPUs that this system has
          # multiplied by this percent. A higher value here will allow PhotoStructure to
          # run more tasks in parallel, but may impact your system's responsiveness. 75%
          # should be a reasonable balance between keeping your system responsive and
          # importing your library quickly. Setting this value to 0 will still allow 1
          # task to run concurrently. System memory will also be taken into account to
          # try to prevent swapping.
          #
          # Min value: 0
          # Max value: 200
          #
          # PS_CPU_LOAD_PERCENT="75"

This can be set to any number between 0 and 200, but I’d try bumping it up to 100 first. Values higher than 150 are probably only good for VMs, really.

Make sure the ventilation around your computer and drives is good, and expect Windows to be laggy with respect to user input if this is set to 100 or higher.