Egregoros

okay doubled the number of open postgres connections. hopefully 40 will be more than enough to handle any sort of natural cavalry that slams fanimations

@kirby I've noticed this too. When Mastodon sees your post for the first time, it starts making various queries, some of them are expensive (e.g. fetching replies). When hundreds of Mastodon servers do this at the same time, the instance may become unresponsive.

In my case, the bottleneck is likely the number of database connections in mitra's connection pool, which by default is proportional to the number of CPU cores. How many CPU cores do you have on your machine?

@silverpill @kirby It's the click of death, you can't really do much about it besides in-memory caching objects and actor representations. The load can easily go to 500 r/s for 30 seconds or more.

@phnt @kirby There is still a couple of low-hanging fruits in mitra. For example, object ID lookup results in a database query that loads an entire thread (similar to /api/v1/statuses/{status_id}/context).