Skip to content
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

[Service Bus] Update perf tests to use a single sender for all instances #14460

Merged
4 commits merged into from
Mar 30, 2021

Conversation

HarshaNalluru
Copy link
Member

  • Imports v7 in the v1 tests to allow creating the resources
  • Makes sender static in both v1 and v7

@@ -8,6 +8,7 @@
"license": "ISC",
"dependencies": {
"@azure/service-bus": "^1.1.10",
"@azure/service-bus-v7": "npm:@azure/service-bus@^7.0.3",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow, did not know you could do this!

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Learned it yesterday! :)

All hail npm! All hail SOF!!!


export abstract class ServiceBusTest<TOptions> extends PerfStressTest<TOptions> {
sbClient: ServiceBusClient;
static sbClient: ServiceBusClient = new ServiceBusClient(connectionString);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason not to do this in globalSetup()?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't matter. It would work the same way.

In my mind.. I've kept globalSteup for creating the resources and the initialization of clients at the static variable declaration itself.

Copy link
Member

@richardpark-msft richardpark-msft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Had a small comment that's mostly just consistency, not functionally affecting that I can see.

@ramya-rao-a
Copy link
Contributor

@HarshaNalluru Can this be merged?

@ghost
Copy link

ghost commented Mar 30, 2021

Hello @HarshaNalluru!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@ghost ghost merged commit 2e61819 into Azure:master Mar 30, 2021
jay-most pushed a commit to jay-most/azure-sdk-for-js that referenced this pull request Apr 26, 2021
…ces (Azure#14460)

- Imports v7 in the v1 tests to allow creating the resources
- Makes sender static in both v1 and v7
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants