@tuxinator So at first, they did. However the problem persists after both setting the max heap size (to 1 gigabyte) and rebooting—specifically the issue is that the sidekiq process running the scheduler runs an IndexScheduler process that balloons to eat all available RAM when left alone. I'm pretty mystified as to why this is happening, honestly!
=> More informations about this toot | View the thread | More toots from somnius@merveilles.town
=> View tuxinator@merveilles.town profile
text/geminiThis content has been proxied by September (3851b).