On May 1, 2:36 pm, Jorge Vargas <[email protected]> wrote:
> The answer is "it depends" both setups you explain below are good and
> valid and it really depends on your system/software/personal
> experience. I have apps running with both setups.
>
> in general paster > mod_wsgi out of the box for small sites. mod_wsgi
>
> > paster ones you know what you are dealing with.
>
> More details below
>
> On Wed, Apr 29, 2009 at 3:55 PM, Derick Eisenhardt
>
> <[email protected]> wrote:
>
> > I'm getting ready to setup a site that could potentially have quite a
> > bit of traffic (at least in bursts). I've already decided I want to
> > use nginx as my front-end/reverse-proxy server. However, I'm not sure
> > what my setup should be beyond that.
>
> You should also configure nginx to serve all your static content, that
> is one of the biggest advantages of it.
>
>
>
> > I've already done a successful test simply using nginx to proxy to a
> > standard paster/virtualenv setup. Would it be faster/more efficient to
> > use Apache + modwsgi, as from what I'm reading Apache is multi-
> > threaded and paster isn't?
>
> actually this is incorrect. paster is multithreaded, but apache is
> able to run in multiprocess mode which on linux is better than
> threads.
Except to the extent described in:
http://blog.dscpl.com.au/2009/03/load-spikes-and-excessive-memory-usage.html
Yes it is mainly focusing on mod_python, but embedded mode of mod_wsgi
has the same issues.
So, Apache configuration is quite important if using prefork and
embedded mode. That or make sure you have lots of memory.
Graham
> > I'm also unsure as to how that works. It
> > appears when using Apache+modwsgi it replaces paster, or do you still
> > have to run paster too, thus effectively running 3 different services?
>
> yes you get rid of paster and use modwsgi as your wsgi server, there
> is an article/program in the docs that sets this up for you.
>
> > My current assumption is if there's alot of cacheable content Paster +
> > nginx would be just fine, but if I'm gonna have a bunch of unique,
> > user specific requests I'd probably want to use Apache/WSGI + nginx.
>
> the bottom line here is that a badly configured apache+mod_wsgi could
> scrawl while a stock paster is good.
>
> > Am I right? And come someone with more experience please expound on
> > this?
>
> hope that helps.
>
> > thanks!
> > - Derick
>
> > PS: We really really really need some guides/faqs/how-tos in the new
> > TG2 docs about such topics (most of the info I've found came from
> > mailing lists or the Pylons site)
>
> Totally agreed, deployment is probably the worst part of our docs.
> It's probably because we have so many alternatives that it hurts, but
> we should have documentation of at least those two options.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
