system pegged on initial import - unRAID
trying to sync recent items folder from google photos via the mobile app. The entire system is pegged at 100 and only a few dozen photos imported over an hour or two.
Is there a way to improve the efficiency of this process? I know we don't support coral, but is there something else that can be done?
I've tried passing --memory=4G as an extra parameter and have cpu pinning on 2 of 4 but it doesn't seem to be respecting that as it pinned itself and brought the system down again.
18 Replies
:wave: Hey @KingEaston,
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.How much resources have you given it? Import is an intensive process
You can look at GPU acceleration which we do support
Any system limits would be set on the docker side and not up to immich. You can review our FAQ as a starting point
i had ram=4G and pinned to 2 cores.
going to try faq settings now....
That’s pretty low. Normal to be pegged
No, it was pegged wide open, which is 8GB ram and 4 cores. I was trying to limit it to 4GB and 2 cores so the rest of the system can still function.
I'm looking at the FAQ's more closely now
If you're running facial detection and smart search at the same time that'll likely be problematic
does anyone know how to apply the docker-compose limits in unraid? Not sure where/how to handle this. The only setting is see to otherwise change from the FAQ's is the Video Transcode Settings -> Threads
Are you limiting your concurrent jobs? That'd be another way about limiting used resources
yes, sorry I did limit each in there to 1 concurrent
system is still not usable
Is your database on a hard drive?
yes, on an unraid array
Would very much recommend moving to an SSD. Likely your database can't keep up is a big issue.
to be clear, we're talking about the database, not the images themselves? Is that correct?
Since this is an initial import I'd pause some jobs so it could run without loading ML and face detection into memory.
At idle my immich instance is using 2.36gb ram. Another 1.6 for processing tasks seems low
(assuming you're using the default clip model as well)
so, turn off those options, run the import, then turn them on 1 by 1 in the future, right? (in addition to possibly moving something to ssd)
Correct. DB should be on an SSD, it will get overwhelmed on initial import if on a HD. Images can be on spinning disk just fine. (For speedier scrolling best to have thumbs on the SSD as well.)
That's what I did