But the recent Mastodon upgrade has caused a significant amount of performance degradation, and I think the only way to really solve it is going to be to throw a lot of money into hardware.
> So the usage patterns [of mastodon.social and botsin.space] are very different, and I think it's safe to say the the mastodon codebase is tuned for mastodon.social and not a weird freaky server like botsin.space.
That's very generous of them, but I'm still inclined to assume Mastodon is being myopic to different usage patterns than their own, resulting in those patterns being needlessly inefficient (and therefore expensive). Especially if it only became a problem after an upgrade.
Gregory's Server
@capital
> So the usage patterns [of mastodon.social and botsin.space] are very different, and I think it's safe to say the the mastodon codebase is tuned for mastodon.social and not a weird freaky server like botsin.space.
That's very generous of them, but I'm still inclined to assume Mastodon is being myopic to different usage patterns than their own, resulting in those patterns being needlessly inefficient (and therefore expensive). Especially if it only became a problem after an upgrade.