Allow custom worker count on sidekiq

Bug #1830894 reported by Benjamin Allot
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Discourse Charm
New
Undecided
Unassigned

Bug Description

Hello,

Following a memory shortage on a discourse unit, I found out that sidekiq was the culprit.

The upstream bug is referenced here: https://github.com/mperham/sidekiq/issues/3824

There isn't a clear winner for the bug resolution among:
* the worker count reduction
* the switch to jemalloc
* the upgrade of sidekiq/ruby

I propose that this bug addresses the first one, which is yet another option to possibly customize the
systemd unit rendered for sidekiq.service

Let me know if you need more details.

Regards,

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.