-
-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Slow performance after a few uses #803
Comments
Immich-go itself need some time at startup to build file indexes. Once done, it just feed immich with images. Note that movie files are longer to process on the server side. |
No, this is the upload phase that's slow. Again, I did a few 2gb takeout files to test the waters and they were lightning fast. Started getting progressively slower. Now it's a crawl. Edit: I did have a remote server doing the machine learning and I thought that might be it, but sadly no. |
Immich-go just passes the file to the server. It depends on the server speed, except for the file indexing at startup. |
Thanks, I'll have to keep investigating. I've confirmed full Gb transfer rates via Libre and transferred a folder tree with thousands of images and it goes very fast. For some reason I'm still very sluggish on immich-go; approximately 8s per image. |
Follow up - it seems closing all other docker containers running has boosted my performance considerably. It's now 1-3s per image. |
Better, but still not fast. You can allocate more ram to immich to see if it helps |
Awesome work. It worked amazing on my first couple of takeouts. I didn't do the wildcard for all of them because I wasn't sure how it was going to work. After doing a few 2gb takeouts, the speed went to a crawl. Like 1 asset every 10s. I even deleted previous uploads so there was no conflict with previous versions. Restarted the PC and my Synology; still a crawl.
Thank you for the great work, I'm not sure what I'm missing.
The text was updated successfully, but these errors were encountered: