On Nov 9, 5:15 am, Greg Milby <
gmi...@gmail.com> wrote:
> i have apache installed, but i'm not sold on apache with wsgi (from the
> little i've read on it [people say it creates a lot of load/threads/bulk and
> the memory is not handled well by apache])...
That is FUD.
If you configure Apache/mod\_wsgi appropriately there is no problem
and is comparable to other solutions.
People who say that tend to be people who can't be bothered to read
documentation properly and set up their systems in a sensible way for
the type of application they run.
For a description of some of the issues that can come up due to poor
choice of configuration see:
http://blog.dscpl.com.au/2009/03/load-spikes-and-excessive-memory-usage.html
In short, ensure your application is thread safe, use worker MPM for
Apache and daemon mode for mod_wsgi and you shouldn't have an issue.
If in a memory constrained system or what to get the most out of
Apache/mod_wsgi then use a nginx front end to handle static files and
proxy to Apache/mod_wsgi. This gives better static files sharing
performance and isolates your web application running on back end
server from slow HTTP clients.
Graham
> on the other hand, if i
> remember correctly, i heard that lighttpd did great... if running them
> in tandem will not cause any problems, i may do that (each on it's own
> port)
>
> On Sun, Nov 8, 2009 at 12:54 PM, Angelo Gladding <
ang...@gladding.name>wrote:
>
>
>
> > Do you *desire* to use a webserver? If so, installing lighttpd or Apache
> > using your standard package manager, apt-get for ubuntu, will do the dirty
> > work of setting up your Upstart or /etc/init.d.
>
> > To be clear, this is the advisable method of deployment.
>
> > On Sun, Nov 8, 2009 at 9:33 AM, Greg Milby <
gmi...@gmail.com> wrote:
>
> >> if memory serves, i think i saw 'setup instructions' for these options on
> >> the webpy site... i will probably trying everything - see what works best
> >> (for me). thanks for replying.
>