Load Testing
Overview
Load testing will be performed to ensure the ticket submission system can perform under expected loads.
Due to the nature of the dev and QA environments, load testing will be performed against stage.cssupport.starwave.com. This, however, implies load testing against production databases. The load testing is not intended to be destructive as it is a shared, production environment. However, since the test is to uncover any potential performance issues, there is risk involved.
Risks
Due to the nature of the environment chosen for load testing, there are certain risks.
| Risk | Symptoms | Mitigation Plan |
|---|---|---|
High load on production database: teamdbmaster.lv2.clubpenguin.com |
|
|
| High load on production mail server: mail01.lv2.clubpenguin.com |
|
|
| High load on stage.cssupport.starwavecom |
|
|
Test Configuration
- Setup Postfix on mail01.lv2.clubpenguin.com as per the Postfix section on CS Tools 4.x Java Server
- Only qatest@clubpenguin.com should be configured to use the cstools transport
- Ensure /etc/disney/cstools/curl/put-ticket-queue has correct values for
- url: https://stage.cssupport.starwave.com:8443/cstools/ticket/v1/queue
- user: To be determined
Tests
Tickets per Minute
| Attachments? | |||
| No | 5MB | 10MB | |
| Min | 11 | 11 | 11 |
| Good | 20 | 20 | 20 |
| Ideal | 60+ | 60+ | 60+ |
A small sample of tickets will be created for each attachment size category:
- One attachment at maximum ticket size
- Ten attachments, totaling maximum ticket size
- Fifty attachments, totaling maximum ticket size
A script will need to be developed to send a number of tickets in parallel.
There will be two rounds of testing – against the API directly and through the mail server. This is so that we can identify if the API or network infrastructure is a bottleneck should we not achieve target processing rates.