Opening an album with more than 300 photos is slow.
After the album contains more than 300 photos, there is a noticeable delay when opening the album. It takes 43 seconds to open a 2000 photo album.
The server's CPU and memory performance are normal. My server has a 128-core CPU, 128 storage, and 10T storage.
Is there any optimization method?
9 Replies
:wave: Hey @JosWei,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.That’s very slow. Is your Postgres database on a hard drive? Or where is it stored
All my servers are deployed on VMware vSphere.
Ok but what kind of storage is backing your database ?
Local, network, SSD, HDD etc
Also, is this app or web?
For refernce, both on Web and App I have instant opening for albums with > 5000 images, both locally stored and remote
with SSD storage and local access ^
Thanks，I would like to know what device your servers is installed on and what is the CPU、 memory performance?
We are currently using Storage Area Network(SAN), HDD hard disk.
Ok, that’s bad. The database should be stored on a local storage ALWAYS, not network, and ideally a SSD
So that’s almost certainly the cause of this
But if you’re using a SAN you should know this / be well ahead of our support here
As we continued to test, we found that only a small number of albums had this type of problem, and most albums with more than 1,000 photos were normal. I tried to create a new album and then put the photos from the problematic album into the new album. The problem still existed.
Now we seem to have found the problem. When the album in question is opened, the statistics are wrong, and the number is large. The album has only 489 photos, but when it opened, it showed 239,121 of them were opening. Albums that can be opened in time do not have this phenomenon. I'm not sure what caused the problem.
