Re: Pyinotify and runserver performance with django channels in docker for mac

ndrew > > On Wed, Jun 14, 2017 at 12:55 PM, qnub > > wrote: > >> Thank you, finally i've checked it and looks like it helps (hope it works >> faster not because of my hardware upgrade but because of Reis usage). So >> with redis page loads in 10 seconds inste

Re: Pyinotify and runserver performance with django channels in docker for mac

gt; > OK, can you try using the Redis one instead and seeing if that's faster? > Docker for Mac has a bit of an odd filesystem and kernel and it's possible > the IPCLayer is not working well underneath it. > > Andrew > > On Thu, Jun 1, 2017 at 10:11 AM, qnub > >

Re: Pyinotify and runserver performance with django channels in docker for mac

sported. > > Andrew > > On Thu, Jun 1, 2017 at 1:36 AM, qnub > > wrote: > >> Not sure what exactly wrog here, but installing pyinotify not helps to >> lower CPU usage in docker on mac OS. As i understand after googling >> installing of `pyinotify` helps

Pyinotify and runserver performance with django channels in docker for mac

Not sure what exactly wrog here, but installing pyinotify not helps to lower CPU usage in docker on mac OS. As i understand after googling installing of `pyinotify` helps in case of running dev server with `runserver` manage command for general django configuration (without channels, but i not

Re: CPU usage by workers

xisted messages. Also CPU usage lowered to the 0-1% So i've just switch all nodes to RedisChannelLayer. On Monday, May 15, 2017 at 8:37:59 PM UTC+6, qnub wrote: > > Thanks for suggestions but i have found nothing suspicious. > > But i've installed pyinotify and switch to ru

Re: CPU usage by workers

ay 10, 2017 at 5:58:38 PM UTC+6, Melvyn Sopacua wrote: > > On Tuesday 09 May 2017 23:21:23 qnub wrote: > > > > > Also it's may be my fault somewhere (and i pretty sure it is). But i > > > not sure where to start my investigation. > > > > I would start

Re: CPU usage by workers

gt; more CPU as connections come through and then disconnect - is it Daphne or > is it runworker? > > Andrew > > On Mon, May 8, 2017 at 5:46 AM, qnub > > wrote: > >> We have executed cluster of 3 docker containers (on separated machines) >> with daphne and w

CPU usage by workers

We have executed cluster of 3 docker containers (on separated machines) with daphne and workers --threads=4 in each container. And this container consube about 15% machine's CPU after start. Then it start consume addtional 4-5% of CPU per new connection and seems like not free this resources wh