1/29/2014

Blitz - Load testing from the cloud

LOAD TEST REPORT

DATE: 1/29/2014 TEST FROM : VIRGINIA
Query URL: http://seedbox.atetracks.ca:80 Started at: Wed Jan 29 2014, 04:47:11 -03:30 Finished at: Wed Jan 29 2014, 04:47:14 -03:30

ANALYSIS
This rush generated 4,333 successful hits in 60 seconds and we transferred 520.78 MB of data in and out of your app. The average hit rate of 72/second translates to about 6,239,520 hits/day. The average response time was 1,378 ms. You've got bigger problems, though: 0.23% of the users during this rush experienced timeouts or errors!

RESPONSE TIMES FASTEST: 102 MS SLOWEST: 3,267 MS AVERAGE: 1,378 MS

TEST CONFIGURATION REGION: VIRGINIA DURATION: 60 SECONDS LOAD: 1-400 USERS

OTHER STATS AVG. HITS: 72 /SEC DATA TRANSFERED:

520.78MB

HITS 99.77% (4333) ERRORS 0.21% (9) TIMEOUTS 0.02% (1)

HITS
This rush generated 4,333 successful hits. The number of hits includes all the responses listed below. For example, if you only want HTTP 200 OK responses to count as Hits, then you can specify --status 200 in your rush.

CODE
200

TYPE
HTTP

DESCRIPTION
OK

AMOUNT
4333

https://www.blitz.io/to#/play

1/3

1/29/2014

Blitz - Load testing from the cloud

HITS

HTTP 200 OK 100% (4333)

ERRORS
The first error happened at 55.00 seconds into the test when the number of concurrent users was at 367. Errors are usually caused by resource exhaustion issues, like running out of file descriptors or the connection pool size being too small (for SQL databases).

CODE

TYPE

DESCRIPTION
Response duration overlimit

AMOUNT
9

ERRORS

RESPONSE DURATION O 100% (9)

TIMEOUTS
The first timeout happened at 60.00 seconds into the test when the number of concurrent users was at 400. Looks like you've been rushing with a timeout of 6000 ms. Timeouts tend to increase with concurrency if you have lock contention of sorts. You might want to think about in-memory caching using redis, memcached or varnish to return stale data for a period of time and asynchronously refresh this data.

https://www.blitz.io/to#/play

RESPONSE TIMES

2/3

1/29/2014

Blitz - Load testing from the cloud

Response Times Users 400

RESPONSE TIMES
3.50 sec 3.00 sec 2.50 sec 2.00 sec

300

200 1.50 sec 1.00 sec 500 ms

100

5 sec

10 sec

15 sec

20 sec

25 sec

30 sec

35 sec

40 sec

45 sec

50 sec

55 sec

1.0 min

The max response time was: 3074 ms @ 383 users

HIT RATE

Hits/sec

Errors/sec

Timeouts/sec 400

80.0/s 300 60.0/s 200 40.0/s 100

20.0/s

0.0/s

5 sec

10 sec

15 sec

20 sec

25 sec

30 sec

35 sec

40 sec

45 sec

50 sec

55 sec

1.0 min

The max hit rate was: 100 hits per second

Powered by www.blitz.io

https://www.blitz.io/to#/play

3/3