3 ms·

Weird. I'm interested to know your setup. Did you use MariaDB or the built in SQLite? I have photoprism running on docker, which is running as a VM on a proxmo

Weird. I'm interested to know your setup. Did you use MariaDB or the built in SQLite? I have photoprism running on docker, which is running as a VM on a proxmox server that is a 13 year old Dell Optiplex 9020. Only 6Gb ram dedicated to the VM (2GB initial, ballon to 6GB), and photoprism uses 2 workers. I have a large 50k set of photo's from starting from when my daughter was born till now (17). I have never sorted through these photo's other than to dump them from my phone every 6 months (camera before smartphones become common). Initial import took less than 45 minutes and that was before tweaking settings. Full manual index with all options, still takes less than 45. Initial face recognition was about 33 people, once I tweaked settings, it's recognized 97 people with little input from me other than tagging the name correctly for a few photo's per person. The only difference in my docker file vs the official are optimized settings, and I'm using a separate VM for the database server as I find multi tendency and backups easier with a VM. (VM only has 2GB ram allocated to it) I'm extremely happy with it, as I always put off organizing my photo collect due to how massive it is. It's made the task so much easier. I am however always looking for other tools. I'm interested in give yours a try, just wanted see what could be the massive difference in experiences.

alias_neo 4y ago
I don't remember specifics, though I can find out; I have it seemed in Kubernetes with hand written manifests. I had to tie Photoprism to a specific node which had had more resources than it's peers; I would have to refer to the manifests to recall which DB I used. All storage was over NFS (meaning the storage speed was limited by my 1Gb network backbone), which probably created some of the resource issues. Edit: as for my tool, it won't replace Photoprism, its primary goal is to deduplicate your photo library.

alias_neo 4y ago

I don't remember specifics, though I can find out; I have it seemed in Kubernetes with hand written manifests. I had to tie Photoprism to a specific node which had had more resources than it's peers; I would have to refer to the manifests to recall which DB I used. All storage was over NFS (meaning the storage speed was limited by my 1Gb network backbone), which probably created some of the resource issues. Edit: as for my tool, it won't replace Photoprism, its primary goal is to deduplicate your photo library.