how many simultaneous workers can we run? about delayed HOT 2 CLOSED

This helps, thanks for the quick reply.

from delayed.

Hey @hknaksu, glad to hear that it's going well so far!

So, I haven't done any extensive profiling on anything other than our in-house deployment (which is Kubernetes-based), but think that the best way to utilize all of your cores is to spin up at least as many workers as there are cores. Ruby's global interpreter lock will prevent the threads themselves from benefitting from more than one core (so max_claims can only allow you to scale up concurrency on a single core). Therefore, running 10 or more workers on a relatively hefty server does seem reasonable to me.

That said, whether or not there are any adverse effects will depend heavily on the footprint of your app, and what kinds of jobs are being run. If the jobs are very DB-intensive, then you might see your DB CPU max out during periods of heavy background work, which could impact your web processes. And since these workers will be sharing resources on the same server, you may also hit up against memory or CPU constraints with the worker processes themselves. At Betterment we do regularly scale up to hundreds of workers, but they are distributed across multiple k8s nodes, so we mostly worry about running too many database-bound jobs at once.

from delayed.