Skip to content

Update testing-scenarios adding more load testing options #4922

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mauroservienti merged 2 commits into from
Apr 2, 2025
Merged

Update testing-scenarios adding more load testing options #4922

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d90e8c5
Update testing-scenarios adding more load testing options
mauroservienti Apr 2, 2025
b388a78
Tweaks
andreasohlund Apr 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions docs/testing-scenarios.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,20 +53,25 @@ A long (though not exhaustive) list, although not every change will merit runnin

Try to break ServiceControl instances by gracefully (CTRL+C) and ungracefully (kill) processes to validate if both storage and logic behavior correctly. This type of testing is very difficult to automate.

- [ ] Ingestion, have the smoketest tool or the load generator generator create a large number of messsages:
- [ ] Ingestion, have the smoketest tool or the load generator generator create a large number of messages:
- [ ] Gracefully stop (CTRL+C) processes
- [ ] Ungracefully (kill) processes
- [ ] Retry groups, create a large retry group and interrup these:
- [ ] Retry groups, create a large retry group and interrupt these:
- [ ] Gracefully stop (CTRL+C) processes
- [ ] Ungracefully (kill) processes

## Performance / load testing
## Performance/Load testing

Test the new version against the previous version.

- [ ] Test performance with a clean database
- [ ] Test performance with a moderate database that exceeds the RAM of the machine
- [ ] Test performance of a large database that exceeds
- [ ] Test performance of a large database that exceeds 500 GB
- [ ] Test stability by:
- [ ] Rebooting the machine and verifying that ServiceControl instances start in a reasonable amount of time and behave correctly
- [ ] Stopping ServiceControl Windows services, verifying they stop as expected, and subsequently start in a reasonable amount of time and behave correctly
- [ ] Killing the hosting virtual machine from the Azure portal and verifying instances behave correctly after the reboot
- [ ] Trying to upgrade instances to newer versions while ingestion runs at full speed under load and verify the upgrade is successful

Review CPU/RAM utilization and disk IO.