Tootfinder

just tweaked/upped web concurrrency and max threads settings in my .env.production settings for Mastodon to give #footiMac a few more processes to handle requests and things are humming along nicely.
I think a big takeway for me on this #selfhost journey is that except on the very smallest one person and minimal followers instance, the database (and possibly redis) function should always be on a different machine or container from mastodon.
#footiMac was clearly having real trouble handling the database activity once it got busy. Even with an SSD now with two bad blocks (which may have been caused by that over-activity), it is way more stable.
#newOldiMac #docker #mastoAdmin #colima #iMac

It's a day later and #footiMac and #newOldiMac are still up and running. Disk usage is stable. Current RAM usage for the database has gone up to 3GB from 1GB since 9PM last night. I'd like to know why. It's not any busier.
I'm running the backup script then later today I'll see if I can investigate more on why the RAM usage fluctuates so much.
I would like to know why it is more stable. Is it because I've simply given it enough room to expand and contract in the colima VM?
Is it because I set the clocks to the same timezone?
Inquiring minds... but I am happy that it is happy. And I have learned a lot and gotten more comfortable with docker. Which has been a goal almost since I joined Mastodon in Nov 2022.
I’m hoping to look for a new macMini now to replace #newOldiMac. If I can get that an SSD to replace the failing SSD in #footiMac and a large HDD for backup that'd be great.
#docker #mastoAdmin #colima #iMac