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 <[email protected]> wrote: > Yes, because it's dev environment with single node but with `rundelay` we > use `asgi_ipc.IPCChannelLayer` > > On Thursday, June 1, 2017 at 11:03:09 PM UTC+6, Andrew Godwin wrote: >> >> Can I ask what channel layer you are using? That's what affects the speed >> of messages being transported. >> >> Andrew >> >> On Thu, Jun 1, 2017 at 1:36 AM, qnub <[email protected]> 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 in case of running dev server with >>> `runserver` manage command for general django configuration (without >>> channels, but i not checked it because i need channels), but looks like >>> it's changes nothing when you use `runserver` with `channels`. >>> >>> What i've made — i've created docker (using latest docker for mac) >>> container with image ubuntu/xenial x64 to execute project. And each page >>> (even in admin panel) loads extremely long (about couple of minutes). If i >>> use `--noreload` option it works fast (couple of seconds or less for page >>> load). I mean loading without cache. I've checked in docker container with >>> `inotifywait` and looks like signals works correctly for file changes, but >>> project works slow even with installed `pyinotify` globally and in project >>> virtual environment. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at https://groups.google.com/group/django-users. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/django-users/61650182-e93b-4a68-ade8-58c3ea18ef31%40googlegroups.com >>> <https://groups.google.com/d/msgid/django-users/61650182-e93b-4a68-ade8-58c3ea18ef31%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-users/937cb35a-8e97-450d-9e0c-c2ce766d7e78%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/937cb35a-8e97-450d-9e0c-c2ce766d7e78%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFwN1updLAHtP5xrUMKPW7h2qEe%3DM0Fk9BzBF%2B2PCa2B5hoP0w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
