And I have just twi tables + web2py auth default models. Single request is quite fast, this is why my personal feeling from app(working with app via browser) is very good. But under the preassure speed goes down.
David On 12 srp, 16:56, mdipierro <[email protected]> wrote: > Here are the logs for my web server running web2py.com. The log only > shows dynamic pages most of which (like the book) use db. > > http://web2py.com/examples/static/logs.txt > > Most pages take around ~20ms but this is a 600MHz VPS with 384MB Ram. > > On Aug 12, 9:48 am, mdipierro <[email protected]> wrote: > > > > > Something is wrong. In wsgiserver.py set > > > LOGGING = True > > > and look at web2py/httpserver.log > > what times do you get? > > do you have very large model files? > > > Massimo > > > On Aug 12, 9:43 am, David Marko <[email protected]> wrote: > > > > I just moved my first real-life app into production (its a private app > > > so I cant share screens etc.). Its running latest stable web2py on > > > Debian 5 + Python 2.6.5 + modwsgi 3.3 . When testing application home > > > page, where are no sql commands, session is disabled (by > > > session.forget()) and migration is disabled, I can get, using apache > > > benchmark, only 12 req/sec. When I compile app, it increases up to 16 > > > req/sec, but both numbers seems to me very low. Can you share some > > > your experience what one can get from web2py? > > > > Using browser, the application feels very responsive, but I'm just > > > scared (a bit) how this will change when all users start using the > > > app. > > > > My server HW is one processor 3GHz, 1.5 GB RAM. > > > > David
