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

Event Hubs: Investigate performance test results #20828

Closed
Tracked by #18819
conniey opened this issue Apr 20, 2021 · 1 comment
Closed
Tracked by #18819

Event Hubs: Investigate performance test results #20828

conniey opened this issue Apr 20, 2021 · 1 comment
Assignees
Labels
amqp Label for tracking issues related to AMQP Azure.Core azure-core Event Hubs pillar-performance The issue is related to performance, one of our core engineering pillars.

Comments

@conniey
Copy link
Member

conniey commented Apr 20, 2021

Investigate results or create an issue if the bug requires deeper research or a bigger fix.

Dependent on #20791

@conniey conniey added Event Hubs Azure.Core azure-core pillar-performance The issue is related to performance, one of our core engineering pillars. amqp Label for tracking issues related to AMQP labels Apr 20, 2021
@conniey conniey added this to the [2021] June milestone Apr 26, 2021
@conniey conniey self-assigned this Apr 27, 2021
@anuchandy anuchandy self-assigned this Jul 8, 2021
@anuchandy
Copy link
Member

The current status is:

We've implemented two standalone apps to measure the performance of T1 and T2. The apps measure the performance of the "Batch Receive APIs".

There are two use cases under the Batch Receive APIs:

1_. Batch Receive with a timeout (exercises internal no backpressure route).
2_. Batch Receive without timeout (exercises internal backpressure route).

We started with "Batch Receive with a timeout" use case and found a regression, a fix got merged to the main.

With the latest nightly build (mirrors the main branch), we see that performance of T2 for "Batch Receive with a timeout" is on par with T1. The Apps used for this are: T1_App, T2_App.

The version of nightly build used for the measuring "Batch Receive with a timeout" can be pulled by adding below repository and dependency:

<repository>
  <id>azure-sdk-for-java</id>
  <url>https://pkgs.dev.azure.com/azure-sdk/public/_packaging/azure-sdk-for-java/maven/v1</url>
  <releases>
    <enabled>true</enabled>
  </releases>
  <snapshots>
    <enabled>true</enabled>
  </snapshots>
</repository>
<dependency>
  <groupId>com.azure</groupId>
  <artifactId>azure-messaging-eventhubs-checkpointstore-blob</artifactId>
  <version>1.9.0-alpha.20210726.1</version>
</dependency>

Currently, we're modifying the app to validate "Batch Receive without timeout" to understand what to fix in this use case.

@conniey conniey modified the milestones: [2021] June, [2021] September Aug 24, 2021
@conniey conniey closed this as completed Sep 2, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
amqp Label for tracking issues related to AMQP Azure.Core azure-core Event Hubs pillar-performance The issue is related to performance, one of our core engineering pillars.
Projects
None yet
Development

No branches or pull requests

2 participants