Tootfinder

welp.
#footiMac remains in a state. If you are reading this, that is a small victory :)
I tried a few things but it remains burdened by I/O activity.
it was still overwhelmed even when I shut down mastodon and nginx so I think it is either the constant sftp traffic or something related to the update to Trixie that I am as yet unaware of.
Regardless, I am taking the opportunity to create docker containers on another machine for postgres and redis to live on.
I'm now waiting for a database dump to complete so that I can try migrating those services over and leaving footiMac to only do nginx and sidekiq
Probably work on it some more tomorrow. Until then this account will be up and down. But at least I'm learning and that's what I like to do.
#mastoadmin

so far so good. #footiMac and #newOldimac are stable and services are being restarted periodically.

dare I say the #footiMac #newOldiMac combo are currently delivering snappy mastodon performance.
#mastoAdmin #selfhost

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

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

I think it is funny, ironic, nerdy, and meta (the proper literal sense) that I have maxed out the 2017 iMac by wanting to install btop while watching it be maxed out on htop.
And yet... it's still posting this, so if stuff doesn't break down now, surely it never will? Even the swap is having a moment. Ooof. I need to be nicer to my machines. lol
#newOldimac #selfhost #mastoAdmin #footiMac #docker #colima #homebrew

ok. *this time* i think my #selfhost is going to be stable or at least self-recoverable. Both #footiMac and #newOldiMac are now set to periodically restart to catch any times when the become unresponsive or colima dies.
#mastoadmin