Done. Please see section 'Complete Minimalist Lighttpd Configuration File' at http://www.web2pyslices.com/main/slices/take_slice/57
I have also added in a section 'Using Lighttpd on port 80 for Secure Web2py admin Access' since it is important to emphasise there should only be one instance of Python running on a tight VPS. John Heenan On Feb 20, 4:11 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > please do. I could use this. > > On Feb 19, 11:35 pm, John Heenan <johnmhee...@gmail.com> wrote: > > > Thanks. > > > From below we get the following resident memory use (RSS) for Apache > > with mod_wgsi and web2py (using Postgre database) > > > 13,888 Apache (=7528+6360) > > 5,612 Some process associated with Apache for wgsi use (wsgi:ip) > > 21,244 Python as launched by Apache for web2py (wsgi:web2py) > > 20,380 Postgre database (=6620+1664+1572+1992+1692+6840) > > -------- > > 61,124 total > > > As indicated below, those who use SQLite for their databse with web2py > > have the RSS use for SQLite included with RSS use for web2py (or more > > accurately the Python process for web2py). > > > One of the issues with Apache is that it launces a new thread to > > service each request. This is inefficient in term of CPU use and is > > likely inefficient in terms of memory use compared to Lighttpd and > > Nginx, which use an event model to service requests. Not only is > > memory an issue on a tight VPS, so also is CPU use. > > > I have started up another VPS and am working on a stripped down /etc/ > > lighttpd.conf file that also includes SSL access. When it is ready I > > will make the file available. > > > John Heenan > -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
