6 ms·
I love immich! On board since June 2026. But, here's a brief report on my evening installation project.. setting up Immich: Ingesting a 1.7TB library (160k+ RAW
by Helmut10001 14d ago
I love immich! On board since June 2026. But, here's a brief report on my evening installation project.. setting up Immich: Ingesting a 1.7TB library (160k+ RAW photos) is apparently not a standard task!
- Thumbnails and ML vectors consumed hundreds of gigabytes. I had to move the library folder to a dedicated ZFS HDD (700GB currently).
- ImageMagick uses 20GB RAM per Nikon RAW file (this triggered the Linux OOM-killer)
- Container crashes filled the OS drive with 2GB _per_ core dump.
I added `ulimits: core: 0` to the `docker-compose.yml` to stop core dumps and increased VM RAM to 48GB. I also added the following `.env` tweaks:
```
NODE_OPTIONS=--max-old-space-size=8192
VIPS_DISC_THRESHOLD=750m
VIPS_CONCURRENCY=1
MAGICK_MEMORY_LIMIT=8G
MAGICK_MAP_LIMIT=4G
```
Also, make sure to limit max logging size in `docker-compose.yml` - this alone cleared up 17GB of logs that were generated in just 4 hours for me:
```yaml
logging:
driver: "json-file"
options:
max-size: "10m"
max-file: "3"
```
Then, setup offsite backups with sanoid/syncoid zfs snapshots in pull zero-trust-mode (next evening project :)