[bitnami/mastodon] Use Ruby with JEMalloc for Mastodon images

[gemelen]

Name and Version

bitnami/mastodon 4.3.3-debian-12-r0

What is the problem this feature will solve?

Using Ruby with a default memory allocator leads to an excessive memory usage by Ruby processes, specifically by Mastodon's Sidekiq - task processing service (and to some extent by Mastodon's Puma - web service).

I went for a memory leak hunt for my installation after a regular Sidekiq outage, where instance regularly exhausted pod memory in a span of a week, leading for a service degradation and a need for manual intervention and/or "restart after X time to prevent outage" solutions.

Additionally,

• Mastodon installation is expected to be run on Ruby with JEMalloc, see documentation
• need to tune the memory allocator for a long-running Ruby application is an industry-known solution

What is the feature you are proposing to solve the problem?

Mastodon image creation uses pre-built Ruby component, which is built using default allocator.
It needs to be replaced with a build configured and built using that allocator library (custom or from a vendor of choice).

What alternatives have you considered?

Creating a cronjob to restart Mastodon services by schedule, which works but is error-prone by itself and needs to be added to the overall setep as a manual step, tailored to a specific environment.

[javsalgar]

Hi,

Thank you so much for the input. So, if I understand correctly, you are proposing that we change the ruby compilation to include jemalloc. Is that correct?

[gemelen]

Yes.

[javsalgar]

Thank you so much, let me create an internal task for the team.