Ok guys here are the results. I repeated and confirmed the results that the great web framework shootout did. Web2py was tested with the application Massimo provided (with couple of fixes that you guys helped me to do). Tests were done in Amazon EC2 M1 Large instance. Because other frameworks were tested using Apache + mod_wsgi combination, web2py were tested the same way. I also wanted to know how fast Rocket was so I tested with it also. All configurations to run web2py followed Massimos complete reference manual 5th edition.
Tests were done with 'ab -n 10000 -c 5' and they were run 10 times. Results are average results from these runs (there were no significant deviations). Here are the results for web2py: "Hello world!"-test: web2py apache + mod_wsgi: 459 requests /second, web2py rocket: 363 req/sec (Django: 2012 req/sec, Flask 1858 req/sec) Template test: web2py apache + mod_wsgi: 344 req/sec, web2py rocket: 292 req/sec, (Django: 925 req/sec, Flask: 1625 req/sec) Database + template: web2py apache + mod_wsgi 274 req/sec (sqlite) and 180 req/sec (DAL), web2py with rocket: 245 req/sec (sql), 171 req/sec (DAL)(Django: 450 req/sec, Flask 1076 req/sec) .oj On Monday, March 4, 2013 10:00:42 PM UTC+2, OJ wrote: > > I will, > > I'm currently figuring out how to arrange my EC2 instance. After that I'm > looking for advice with web2py / Apache setup :) One problem at the time. > > On Sunday, March 3, 2013 3:37:32 PM UTC+2, wwwgong wrote: >> >> Please share the benchmark results when avail > > -- --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
