If the only discussion here is tight vps, then postgresql results should not even come into matter in your bottom line. Taking out 20MB for the postgres process, and add 5 mb for a sqlite in the python/web2py process, thats an extra 15 mb you can play around with. Also, configuring apache to run only a single process (just that root thread instead of two like I have it configured) you reduce the apache footprint to only 6mb. I think a more accurate total would be 40,000.
-Thadeus On Sat, Feb 20, 2010 at 12:11 AM, 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 >> >> On Feb 20, 2:55 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: >> >> > Happy ? >> >> > ps aux | grep "apache" && ps aux | grep "wsgi" && ps aux | grep >> > "postgres" && ps aux | grep "python" >> > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND >> > root 3878 0.6 1.4 145136 7528 ? Ss 22:49 0:00 >> > /usr/sbin/apache2 -k start >> > www-data 3950 0.0 1.2 145288 6360 ? S 22:49 0:00 >> > /usr/sbin/apache2 -k start >> > user 3974 0.0 0.1 7528 892 pts/0 R+ 22:49 0:00 grep apache >> > www-data 3913 0.0 1.0 284396 5612 ? Sl 22:49 0:00 >> > (wsgi:ip) -k start >> > www-data 3915 2.6 4.0 331384 21244 ? Sl 22:49 0:00 >> > (wsgi:web2py -k start >> > user 3976 0.0 0.1 7528 896 pts/0 R+ 22:49 0:00 grep wsgi >> > postgres 3748 2.4 1.2 102008 6620 ? S 22:49 0:00 >> > /usr/lib/postgresql/8.3/bin/postgres -D /var/lib/postgresql/8.3/main >> > -c config_file=/etc/postgresql/8.3/main/postgresql.conf >> > postgres 3750 0.0 0.3 102008 1664 ? Ss 22:49 0:00 >> > postgres: writer process >> > postgres 3751 0.0 0.2 102008 1572 ? Ss 22:49 0:00 >> > postgres: wal writer process >> > postgres 3752 0.0 0.3 102284 1992 ? Ss 22:49 0:00 >> > postgres: autovacuum launcher process >> > postgres 3753 0.0 0.3 72632 1692 ? Ss 22:49 0:00 >> > postgres: stats collector process >> > postgres 3963 0.3 1.3 103992 6840 ? Ss 22:49 0:00 >> > postgres: user mydata 127.0.0.1(35324) idle >> > user 3978 0.0 0.1 7532 908 pts/0 R+ 22:49 0:00 grep postgres >> > user 3980 0.0 0.1 7528 896 pts/0 S+ 22:49 0:00 grep python >> >> > -Thadeus >> >> > On Fri, Feb 19, 2010 at 10:41 PM, John Heenan <johnmhee...@gmail.com> >> > wrote: >> > > I do not accept the data below as complete for comparative purposes >> > > since we do not know what the memory use by Apache proper itself is. >> >> > > The figures we are using to add up memory use for web2py are resident >> > > memory (RSS) for >> > > web server for web2py >> > > + python for web2py >> > > + database for web2py >> >> > > RSS for sqlite database use in web2py is included with Python RSS >> >> > > Using the RSS numbers from Thadeus below this is what I get >> >> > > 20,820 Python as launched by Apache for web2py (wsgi:web2py -k start) >> > > 20,236 (=6620+1756+1572+1992+1692+6604) for Postgres database >> > > Data missing: Apache proper web server RSS use >> >> > > John Heenan >> >> > > On Feb 20, 7:33 am, Thadeus Burgess <thade...@thadeusb.com> wrote: >> >> > >> ps aux | grep "wsgi" && ps aux | grep "postgres" && ps aux | grep >> > >> "python" >> > >> USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND >> > >> www-data 3949 0.2 3.9 330988 20820 ? Sl 15:27 0:00 >> > >> (wsgi:web2py -k start >> > >> ********* 4030 0.0 0.1 7528 892 pts/0 R+ 15:30 0:00 grep >> > >> wsgi >> > >> postgres 3768 0.3 1.2 102008 6620 ? S 15:26 0:00 >> > >> /usr/lib/postgresql/8.3/bin/postgres -D /var/lib/postgresql/8.3/main >> > >> -c config_file=/etc/postgresql/8.3/main/postgresql.conf >> > >> postgres 3771 0.0 0.3 102008 1756 ? Ss 15:27 0:00 >> > >> postgres: writer process >> > >> postgres 3772 0.0 0.2 102008 1572 ? Ss 15:27 0:00 >> > >> postgres: wal writer process >> > >> postgres 3773 0.0 0.3 102284 1992 ? Ss 15:27 0:00 >> > >> postgres: autovacuum launcher process >> > >> postgres 3774 0.0 0.3 72632 1692 ? Ss 15:27 0:00 >> > >> postgres: stats collector process >> > >> postgres 4025 0.1 1.2 104012 6604 ? Ss 15:30 0:00 >> > >> postgres: servant mediapanel 127.0.0.1(57909) idle >> > >> ********* 4032 0.0 0.1 7532 908 pts/0 S+ 15:30 0:00 grep >> > >> postgres >> > >> ********* 4034 0.0 0.1 7528 888 pts/0 R+ 15:30 0:00 grep >> > >> python >> >> > > -- > > -- > 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. > > -- 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.
