-
Granted, it's a huge library! But I finished indexing quite a while ago and things are otherwise running well (it was mostly fine during the indexing too). Many/most have GPS tags. From PHOTOPRISM_DEBUG: "true" it's clear that it's actually doing something useful; it's doing about once a second "generating title from label" or "approximate position of uid is...". I assume it's enriching the database and things are kind of working as expected but maybe I'm missing some optimization, we can add some index to the db or something. I hope it's not the debug that makes it slow, one line per second. Or at least a way to gauge progress (I didn't capture the output, probably I could tell how many uids were processed). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
First of all, make sure to use our latest version as we optimized a few things. Then try disabling location estimates on https://demo.photoprism.org/settings/library - those usually cause most of the load. Metadata updates now generally happen more often as photo titles get regenerated after people were recognized so that they contain the names. While I don't see such a high load with 100k images on our Core i3 test server, it's absolutely possible that you have a different experience with 400k images and/or other hardware, see #1618 (comment) With that many files, it may also be worth increasing the InnoDB buffer size: PS: Please share your server specs (OS, CPU, disk type and memory) so that we can better reproduce your issue. |
Beta Was this translation helpful? Give feedback.
First of all, make sure to use our latest version as we optimized a few things. Then try disabling location estimates on https://demo.photoprism.org/settings/library - those usually cause most of the load.
Metadata updates now generally happen more often as photo titles get regenerated after people were recognized so that they contain the names. While I don't see such a high load with 100k images on our Core i3 test server, it's absolutely possible that you have a different experience with 400k images and/or other hardware, see #1618 (comment)
With that many files, it may also be worth increasing the InnoDB buffer size:
https://mariadb.com/kb/en/innodb-buffer-pool/#innodb_buffer_pool_size
P…