-
Notifications
You must be signed in to change notification settings - Fork 2k
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.
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
Add stress tests module for Service Bus #29407
Conversation
458a8b9
to
c50c222
Compare
c50c222
to
4ad9809
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! Just one comment
}) | ||
.buildProcessorClient(); | ||
|
||
client.start(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to close the client when the program ends?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same with other clients. Does clean-up matter?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll add close()
for sender
and sync receiver
since we know the total send/receive messages. But for processor
and async receiver
, we don't know when we can close it. We keep the processor running until we manually shut down or deploy another test. If someone needs to, they can add a fix duration to processor
test.
The clean-up will not impact test running and its results. Because we will run each test scenraio on different resource groups and all resources are auto-deleted after we end the test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! As per our disscussion, let's add more cases to cover true stress tests scenarios - low memory, CPU restrictions, thread starvation, socket exhaustion, lags, custoffs and so on
Description
Add service bus stress tests project base on azure-sdk-chaos.
Resolve #23953.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines