3 ms·
That's a Mastodon and Rails architecture issue first and foremost, though, and far less of a Ruby issue. Mastodon is indeed a resource hog, so that part of the
by vidarh 4y ago
That's a Mastodon and Rails architecture issue first and foremost, though, and far less of a Ruby issue.
Mastodon is indeed a resource hog, so that part of the complaint I agree with.
I've run queue processing on servers a fraction of a modern server CPU, less memory than that total, and with Ruby 1.8.x.
It's not hard. It's hard to do with a naive Rails-based design based around Sidekick workers and ActivityRecord.