On Fri, May 15, 2015 at 10:33 AM, Tom Evans <[email protected]> wrote: > On Thu, May 14, 2015 at 4:18 PM, Marc Aymerich <[email protected]> wrote: >> On Thu, May 14, 2015 at 11:26 AM, Tom Evans <[email protected]> wrote: >>> On our app servers we typically use Apache with worker MPM and >>> mod_wsgi, although we have a few nginx+uwsgi sites, and I would dearly >>> love some time to play around with a circusd + chausette + celery >>> setup. >> >> >> Hi Tom, >> never heard about circusd and chaussette, but it sounds interesting. >> >> I believe the advantage of this setup pays when you have several >> independent low-traffic applications, because you don't want all of >> them to have preforked wsgi worker processes, not even the master >> process. I think uwsgi can do that (emperor mode, cheaper subsystem), >> but circusd will allow you to do the same which celery (celery needs >> at least one master per pool). Is this the main point? I'm asking >> because I can only find just a couple of blogposts and the >> documentation is concise, neither mention the real tangible advantage >> over traditional deployments. >> > > There are few very cool things I like about circusd + chaussette, > chausette allows you to run over a unix socket, and this allows > circusd to easily spin up a new backend (with different code) and > transfer requests to that unix socket, whilst leaving the old backend > still running. > > This means zero downtime when doing a code upgrade, and instant > failback to the old application if for some reason you don't like what > was pushed. > > The second thing is that circusd is a process manager like > supervisord, but it allows for dynamic operation - you can run celery > worker processes underneath it, and spin up/spin down worker processes > as you see fit to allow for load. > > The third is that circusd is accessed by a web interface, which allows > for simple day to day use and also simplifies how admins and sysadmins > can interact with it. Its very easy for our sysadmins to control > things they can just fire http requests at. >
thanks Tom, that is really cool, I really appreciated your comments on this! -- Marc -- 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 http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2BDCN_t886rR7b88H7oBYXGJTUBFA0wsxe9c6p8vK4G_7b2d9g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
