@voltron Which database? Perhaps you need indices or a connection pool. There should be no problem with 600 visitors/day.
@vince do you have any data we can use to compare web2py to other frameworks? Massimo On Dec 20, 6:30 pm, vince <[email protected]> wrote: > i've been evaluate web2py recently for its performance, so far the > overhead i found is very minimum comparing to other framework. the > only minor issues so far i've found are from the html helper or > sqltable which does require some cpu power. > > 600 visitors a day is very low volume and it shouldn't have any > problem at all even if you just using reverse proxy via apache. maybe > you can try mod_wsgi. > > -vince > > On Dec 21, 5:47 am, voltron <[email protected]> wrote: > > > I am having serious performance problems with an appliance. I have 2 > > instances of web2py being served by reverse proxy via Apache2. > > > The live domain running on port 8000 runs very compared to the test > > domain running on port 8002. The only difference is that the live > > server is being accessed by over 600 visitors a day. > > > The pages are being generated very slowly, even though they do not > > access the db. I have compiled all the appliances concerned but did > > not get any visible speedups. I could start cacheing the pages in ram, > > but I just want to be sure that there are now tips left out before > > doing so. Any other tips? Does emptying the sessions folder help any > > way? > > > Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
