It would be nice to try the same benchmark with postgresql (running locally) and connection pools enabled
DAL(...,pool_size=100) Connections pools are ignored with sqlite because it does not support concurrent requests. Also notice that because of the GIL this benchmark is only using one of the two cores. I added some comments about this too. On Aug 24, 7:14 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > Fantastic. Email me for the edit code. > > On Aug 24, 7:04 am, what_ho <a...@viovi.com> wrote: > > > no problem! > > > correct - 12ms per request is the time I recorded to completely > > process one webpage request, from the start point of the http request > > headers being sent to the server, to the last byte of the HTTP 200 > > response being successfully received by the client. > > > This is using all default settings for session (enabled) etc. and the > > default controller and 'Hello World' view one gets when using the > > admin webpages to create a new application. The only addition to the > > defaults are the 5 dummy table definitions. > > > I have added this to alter ego > > here:http://www.web2py.com/AlterEgo/default/show/248 > > > (Some of the bullet point lists did not come out right in the markdown > > in this article, I will need to go edit at a later date) > > > Here is a full output from the httperf load test tool for the last > > test, compiled with migrate=False on: > > > Total: connections 1000 requests 1000 replies 1000 test-duration > > 12.119 s > > > Connection rate: 82.5 conn/s (12.1 ms/conn, <=1 concurrent > > connections) > > Connection time [ms]: min 0.1 avg 12.1 max 75.3 median 10.5 stddev 6.0 > > Connection time [ms]: connect 0.9 > > Connection length [replies/conn]: 1.000 > > > Request rate: 82.5 req/s (12.1 ms/req) > > Request size [B]: 84.0 > > > Reply rate [replies/s]: min 79.4 avg 84.1 max 88.8 stddev 6.6 (2 > > samples) > > Reply time [ms]: response 11.2 transfer 0.1 > > Reply size [B]: header 391.0 content 5619.0 footer 2.0 (total 6012.0) > > Reply status: 1xx=0 2xx=1000 3xx=0 4xx=0 5xx=0 > > > CPU time [s]: user 1.46 system 5.97 (user 12.1% system 49.2% total > > 61.3%) > > Net I/O: 491.1 KB/s (4.0*10^6 bps) > > > Errors: total 0 client-timo 0 socket-timo 0 connrefused 0 connreset 0 > > Errors: fd-unavail 0 addrunavail 0 ftab-full 0 other 0 > > > On Aug 24, 12:03 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > > Thank you! > > > > Just to clarify. 12ms/request includes the time to define all system > > > tables, your tables, create a new session, execute controller, action, > > > view and layout, not just the time to execute the db.py. Correct? > > > > Can you post your results on AlterEgo? OR would you mind if I post it > > > and quote you as author of the benchmarks? > > > > Massimo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" 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 -~----------~----~----~----~------~----~------~--~---
