Are you using db connection pooling and do you cache your queries? That could help.
On Thursday, April 11, 2013 2:45:41 PM UTC+2, Marco Tulio wrote: > > about 50 to 90% ... > but I see that this is not a problem because of how fast the server > usually answers, this seems to be a problem when the page takes more time > to load a single page. > and it takes around 6 secs to load a page that checks the database. > If I open 5 pages at the same time, it's possible that I get "504 Gateway > Time-out" on at least 1. > > pages that do not consult a database are imediatly served. > > The pages that are giving me more problem consult a database and have 1 > chart (javascript) (similar to google charts). > > I'll do a few more tests changing a few things on those pages... maybe > there's something wrong with javascript or something else that's taking too > much time to load... > > > > > 2013/4/11 Derek <sp1...@gmail.com <javascript:>> > >> and how much ram and CPU does a simple wsgi server use? >> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "web2py-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to web2py+un...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > -- > []'s > Marco Tulio > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
