You are comparing apples with oranges. By bechmarking /examples/ default/index you are not just benchmarking the cherrypy wsgiserver. You have a lot of overhead (sessions, database IO, complex template parsing, file IO, etc.).
There are different issues here: - Cherrypy wsgiserver is probably as fast as Apache+mod_wsgi although not recommended in production (because of all the extra features of apache). Alache should be faster at serving static files because it will bypass some of the web2py logic. - You should make a simpler app and benchmark that - There are many possible optimizations in web2py that I have described in previous posts in this thread. Massimo On Jun 20, 8:21 am, carlo <syseng...@gmail.com> wrote: > Anyway I would be surprised to see CherryPy+SQLite performing slower > than Apache+anything else at least under moderate load. > > carlo > > On 19 Giu, 20:18, Fran <francisb...@googlemail.com> wrote: > > > On 19 June, 16:01, Daniel Guryca <dun...@gmail.com> wrote: > > > > I can see that performance coming from a default integrated server is > > > somewhat poor. > > > 'integrated server' = CherryPy/SQLite, right? > > > > What other deployment possibilities could I test ? > > > ApacheWSGI/PostgreSQL would be a better comparator. > > > F --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@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 -~----------~----~----~----~------~----~------~--~---
