Set Sidekiq Cluster process count to match available CPUs (when standalone)
While doing some testing today I noticed that Sidekiq Cluster will only use one CPU by default as it only has one "worker" (set via queue_groups
).
As such I think we should have Omnibus do something similar like it already does for Puma and for it to scale Clusters process count higher based on the same number of CPUs to ensure there's no performance bottlenecks though this should only happen when Sidekiq is standalone and not being run with other components.