Initial indexing killing my Synology nas (11k IOPS, 250mb/s sustained rw transfer) - is there a way to limit this? about photonix HOT 4 OPEN

I’ve had to stop it on mine for now. It’s running the CPU at a constant 98%. I’ll wait a couple of versions to see if there are improvements.

from photonix.

I’ve seen this as well. What I did was limit the resource priority in the docker containers. At least that way it’s not running the CPU at 100% all the time.

Maybe in future there would be a way to engage the GPU in devices like the 920+ as they have the onboard GPU. They do something like that for rencoding in Tdarr. Maybe thats something to look at?

from photonix.

Same problem here. I was running it in docker containers on my arm server (8 CPUs, 2GB RAM) and started with 100 photos, but it was running the CPU-s on 100% for hours (the server was almost unresponsive). Then, what surprised me was that even after stopping the 3 docker containers, there were a lot of python threads running Photonix tasks. I had to reboot the server.

Do you have some lighter API-s, maybe command-line which deal with applying one task to a photo? I might even contribute some time to the project. I am mainly interested in the automatic tagging.

from photonix.

Yes, you can limit CPU utilisation by using bare minimum supervisord.conf file.
Create your own copy of supervisord.conf (you can delete lines related to program that you dont want to run and keep only config that required to launch UI) and modify docker-compose.yaml file to add your supervisord.conf path in volume section as below:

• /supervisord.conf:/etc/supervisord.conf

To run indexing using cli run below commands:
docker-compose exec photonix ./manage.py

It will give you number of options e.g raw_scheduler, raw_processor, classification_face_detection_processor, classification_object_processor etc.

from photonix.