Have you profiled your application? How many SQL queries is it doing during a request processing cycle?
You could write a web app in pure asm code and still get 1 req/sec if you did something really stupid in your code so it's not generally about Django. Erik On 03.10.2008, at 16:32, Alessandro wrote: > is it normal that a cached page on dreamhost (I'm using passenger to > connect apache and django) > gives this results of 4.9 req/s? > > > httperf --hog --timeout=10 --client=0/1 > --server=www.animalisenzacasa.org --port=80 --uri=/ --rate=5 > --send-buffer=4096 --recv-buffer=16384 --num-conns=200 --num-calls=1 > Maximum connect burst length: 1 > > Total: connections 200 requests 200 replies 200 test-duration 40.823 s > > Connection rate: 4.9 conn/s (204.1 ms/conn, <=9 concurrent > connections) > Connection time [ms]: min 955.0 avg 1016.3 max 1682.4 median 1019.5 > stddev 69.8 > Connection time [ms]: connect 237.6 > Connection length [replies/conn]: 1.000 > > Request rate: 4.9 req/s (204.1 ms/req) > Request size [B]: 75.0 > > -- > Alessandro Ronchi > Skype: aronchi > http://www.alessandroronchi.net > > Rispetta l'ambiente: se non ti รจ necessario, non stampare questa mail > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
