Just a warning in case you are wondering why you haven't got a response yet. I am on the tail end of a US trip and soon to fly home. This is why I haven't responded. I will get to this after I get back home and recover somewhat.
Graham On 05/09/2014, at 3:51 PM, Damien de Lemeny <[email protected]> wrote: > I did, I actually made some improvements on our previously bloated production > setup based on your 2013 talk and a bit of guesswork, but I don't recall > those giving a clear answer to my question. > You usually oppose apache MPM process/thread configurations in embedded modes > to WSGIDaemonProcess process/thread configuration in daemon mode (as far as I > understood, correct me if I'm wrong). > I am just not clearly understanding what should happen to the former > directives when using the latter. > I don't really have a bottleneck to fix here, just trying to get a better > understanding of how things work. > > Thanks again for answering ! > > Le samedi 6 septembre 2014 00:16:06 UTC+2, Graham Dumpleton a écrit : > Until I get a chance to response specifically about it, have you already > watched: > > http://lanyrd.com/2012/pycon/spcdg/ > http://lanyrd.com/2013/pycon/scdyzk/ > > Graham > > On 05/09/2014, at 2:58 PM, Damien de Lemeny <[email protected]> wrote: > >> Note : this is a crosspost from ServerFault >> >> >> Could you please help me understand some aspects about the relation between >> Apache MPM configuration directives and mod_wsgi's daemon mode ? >> >> How to best configure apache mpm when serving only WSGI applications with >> WSGIDaemonProcess and WSGIRestrictEmbedded On ? (these mod_wgsi directives >> are already -- and correctly AFAICT -- configured) >> >> Now what should I do with StartServers, Min/MaxSpareThreads and the other >> Apache level MPM configuration directives ? >> >> As far as I understood, those are usually addressed to properly configure >> processes and threads in prefork/worker embedded mode, but what is their >> influence in daemon mode ? >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "modwsgi" 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/modwsgi. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" 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/modwsgi. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi. For more options, visit https://groups.google.com/d/optout.
