• [^] # Re: Les performances ne sont pas excellentes

    Posté par . En réponse au journal Small Issue Tracker. Évalué à 1.

    ab

    Je ne connaissais pas ab. Intéressant.

    J'ai fait l'exercice, voici le résultat :

    $ ./smitc signin http://smit.herokuapp.com/signin homer homer
signin... args=http://smit.herokuapp.com/signin homer homer
$ ab -c 50 -n 1000 -C sessid=.smitcCookie 'http://smit.herokuapp.com/things_to_do/issues/'
This is ApacheBench, Version 2.3 <$Revision: 1430300 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking smit.herokuapp.com (be patient)
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Completed 500 requests
Completed 600 requests
Completed 700 requests
Completed 800 requests
Completed 900 requests
Completed 1000 requests
Finished 1000 requests
Server Software: 
Server Hostname: smit.herokuapp.com
Server Port: 80
Document Path: /things_to_do/issues/
Document Length: 1408 bytes
Concurrency Level: 50
Time taken for tests: 9.137 seconds
Complete requests: 1000
Failed requests: 0
Write errors: 0
Total transferred: 1471792 bytes
HTML transferred: 1408000 bytes
Requests per second: 109.44 [#/sec] (mean)
Time per request: 456.862 [ms] (mean)
Time per request: 9.137 [ms] (mean, across all concurrent requests)
Transfer rate: 157.30 [Kbytes/sec] received
Connection Times (ms)
 min mean[+/-sd] median max
Connect: 26 44 28.3 36 262
Processing: 235 404 115.1 376 975
Waiting: 225 389 104.2 363 975
Total: 276 449 122.4 411 1007
Percentage of the requests served within a certain time (ms)
 50% 411
 66% 449
 75% 489
 80% 517
 90% 601
 95% 728
 98% 837
 99% 900
 100% 1007 (longest request)

    Que peut-on conclure après ce test ? Est-ce que ça teste plutôt mon appli, plutôt Heroku, ou plutôt le réseau ?