i run it in 4GB of RAM; it does OOM every quarter or so, i've had to restart it 3 times this year. I assume there's something i am doing inefficiently with it, but i suspect it's related to logging. Feels like it OOMs quicker the more i use it, but that's just a hunch.

it probably wouldn't hurt to cron-job a sighup and reissue the start command once a week.

The OOM issue is fixed in the most recent updates -- it was a memory leak linked to the file scanner, IIRC.

I run it with 1GB in a container, no issues. 367 GB, about 36k files