UCDavisLibrary / main-wp-website-deployment

Deployment files and commands for library.ucdavis.edu
1 stars 1 forks source link

Siege Test production system #28

Closed qjhart closed 2 years ago

qjhart commented 2 years ago

We need to validate that the new setup can handle the expected load for the library website on go-live. There are a number of different aspects of this, but this test is just to verify that the server is responding with files fast enough.

Previously, we have used siege testing of the library website for this. I used a similar approach.

The first test was to created a shaped test using semi-expected percentage, based on the main navigation setup. The file is included: shaped_in.txt The siege program downloads all the ancillary files, as can be seen from the files-hit.txt. The second test was a non-shaped test that randomly accessed every permalink on the site. The permalinks where obtained by adding the list-urls plugin to the test computer, activating it, and downloading all permalinks.

I then ran a siege test with both 32 and 128 concurrent users. 32 is a large concurrent load on the current site. Results indicate that the production site will deliver the files in a timely manner.

Results

32 concurrent users:

shaped

Transactions:              70527 hits
Availability:             100.00 %
Elapsed time:             496.33 secs
Data transferred:        4222.42 MB
Response time:              0.19 secs
Transaction rate:         142.10 trans/sec
Throughput:             8.51 MB/sec
Concurrency:               27.28
Successful transactions:       70301
Failed transactions:               0
Longest transaction:           17.61
Shortest transaction:           0.00

unshaped

Transactions:              75004 hits
Availability:              99.98 %
Elapsed time:             694.56 secs
Data transferred:        5361.99 MB
Response time:              0.26 secs
Transaction rate:         107.99 trans/sec
Throughput:             7.72 MB/sec
Concurrency:               28.41
Successful transactions:       74991
Failed transactions:              17
Longest transaction:            4.44
Shortest transaction:           0.01

The failed transactions are primarily missing files from the site.

128 concurrent users:

Note for an extremely heavy load, the overall response time does go up a bit, but the cache kept things relatively smooth.

shaped

Transactions:             282347 hits
Availability:             100.00 %
Elapsed time:            2022.07 secs
Data transferred:       16907.26 MB
Response time:              0.88 secs
Transaction rate:         139.63 trans/sec
Throughput:             8.36 MB/sec
Concurrency:              123.14
Successful transactions:      281462
Failed transactions:               4
Longest transaction:            8.41
Shortest transaction:           0.00

unshaped

Transactions:             298953 hits
Availability:              99.98 %
Elapsed time:            2696.54 secs
Data transferred:       21243.73 MB
Response time:              1.11 secs
Transaction rate:         110.87 trans/sec
Throughput:             7.88 MB/sec
Concurrency:              123.06
Successful transactions:      298892
Failed transactions:              67
Longest transaction:            9.96
Shortest transaction:           0.00
qjhart commented 2 years ago

@spelkey-ucd / @jrmerz let me know if there are any configuration tests, you'd like me to try. Any other suggestions welcome as well.