Re: Django Channels: best way to launch multiple workers

Is there any update on this? Do we have any recommendations now on how many workers can run on a server? On Tue, Oct 10, 2017 at 5:00 AM Andrew Godwin wrote: > I don't have enough hard data to give a recommendation, unfortunately. > > Andrew > > On Mon, Oct 9, 2017 at 7:14 PM, Piet van Leeuwen

Re: Django Channels: best way to launch multiple workers

I don't have enough hard data to give a recommendation, unfortunately. Andrew On Mon, Oct 9, 2017 at 7:14 PM, Piet van Leeuwen wrote: > On a server is there a recommendation for how many workers to have running? > > With Gunicorn we would run... > > def max_workers(): > return cpu_count() *

Re: Django Channels: best way to launch multiple workers

On a server is there a recommendation for how many workers to have running? With Gunicorn we would run... def max_workers(): return cpu_count() * 2 + 1 On Thursday, February 9, 2017 at 11:38:07 AM UTC+13, Andrew Godwin wrote: > > The difference is mostly in Python performance - threading

Re: Django Channels: best way to launch multiple workers

The difference is mostly in Python performance - threading in Python tends to perform worse than using multiple processes, which is why we recommend using multiple processes in the docs. However, you can save a bit of memory usage with threading, so you can use that if you want. I would not, howev

Django Channels: best way to launch multiple workers

What's the best way to launch multiple Django channels workers on a production server to take advantage of extra cores? The documentation says : Each server is single-threaded, so it’s recommended you run around one o