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.
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 thelist-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
unshaped
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
unshaped