2026-09-23 18:54 UTC
@GossiTheDog@cyberplace.social @WTL@mastodon.social out of curiosity, which parts of mastodon are the most memory-hungry? E.g., async queue handlers vs serving the actual app
Replies (1)
-
@mo@mastodon.ml 2026-09-23 19:03
@kboyd@phpc.social the part where ruby doesn't have a modern async runtime, so you have to run multiple processes, each with multiple GIL-interlocked threads, holding multiple postgres connections, which are quite heavy also from what I heard, background job processor can't run too many threads concurrently, so you have to run multiple copies of those, but I haven't retested that on modern versions @GossiTheDog@cyberplace.social @WTL@mastodon.social