Re: Bind Cherrypy process to a specific core

We fire up one process per processor core we want to use, and let the OS
decide how to schedule it. Then we set up NGinx or something to handle the
reverse proxying to the various ports. uwsgi sounds like it might be better
for that, since it can do everything on a single port.


On Fri, Jul 1, 2016 at 4:09 PM Giuliani Sanches <[email protected]>
wrote:

> Hi.
>
> I was reading the history of this group and read that to scale out
> Cherrypy, it's a good practice to start one process per core and adjust the
> thread number.
>
> Do you guys bind each process to a specific core using a tool like taskset
> (Linux) or just start the required process and let to the S.O. decide what
> to do ?
>
> Thank you.
>
> --
> You received this message because you are subscribed to the Google Groups
> "cherrypy-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to cherrypy-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
> To post to this group, send email to cherrypy-users-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
> Visit this group at https://groups.google.com/group/cherrypy-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "cherrypy-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cherrypy-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
To post to this group, send email to cherrypy-users-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
Visit this group at https://groups.google.com/group/cherrypy-users.
For more options, visit https://groups.google.com/d/optout.