up until late about december 2022 we were battling the database server being at 100% load 24/7. turns out you need to actively be repacking your database at least weekly. taking it down and doing a full vacuum helps, but the repack allows you to do it while it’s online.

that being said, there are still some things in pleroma that cause major database issues that i’ve brought up in the past – this for example https://gitlab.com/soapbox-pub/rebased/-/issues/137 – this one particular issue ties up 32-40 database connections at a time, almost 4x what the typical pleroma server has configured for database connections (and would equate to 100% cpu usage on anything <8 threads) for nothing. it’s literally trying to update bookmarks from people who have deleted their accounts or are on instances that are unreachable. its just stupid shit like that