Migrating to VectorChord - Storage Type

Hi all! I'm editing my docker-compose.yml file to update my Immich components and I see there's a new settings preset option:
# Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs
# DB_STORAGE_TYPE: 'HDD'
# Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs
# DB_STORAGE_TYPE: 'HDD'
I'm running Immich on a Synology NAS, with a RAID 5 setup, containing 4 enterprise-grade HDDs. So technically I'm running on HDDs, but they have vastly different performance characteristics than a "normal" HDD. Should I still use this preset? What settings does it apply to the database? Thanks in advance!
6 Replies
Immich
Immich2w ago
:wave: Hey @eden881, 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. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time). 2. :ballot_box_with_check: read applicable release notes. 3. :ballot_box_with_check: reviewed the FAQs for known issues. 4. :ballot_box_with_check: reviewed Github for known issues. 5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy). 6. :ballot_box_with_check: uploaded the relevant information (see below). 7. :ballot_box_with_check: 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. Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
Xiticks
Xiticks2w ago
I think that even bad ssd have higher IOPS than really high quality enterprise grade (whatever you want to add here) HDDs So IMO I would still set HDDs but I might be wrong about what this setting really changes for the database
Daniel
Daniel2w ago
Yeah definitely. Whatever HDD you'll find it won't even get close
eden881
eden881OP2w ago
Oh, it's IOPS related? I thought about throughput. Makes sense. Thanks! 🙏
Daniel
Daniel2w ago
Yeah that's the important part for databases; small random accesses You can obviousy get decent sequential throughput out of a RAID of HDDs
Immich
Immich2w ago
This thread has been closed. To re-open, use the button below.

Did you find this page helpful?