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.

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

Jump to bottom

test: add performance test to check recent 2.x degradation #4751

Open
Totktonada opened this issue Jan 29, 2020 · 1 comment
Open

test: add performance test to check recent 2.x degradation #4751

Totktonada opened this issue Jan 29, 2020 · 1 comment
Labels
performance qa Issues related to tests or testing subsystem
Milestone
wishlist

Comments

@Totktonada
Copy link
Member

The workload is described in #4736.
@Totktonada Totktonada added qa Issues related to tests or testing subsystem performance labels Jan 29, 2020
@Totktonada Totktonada mentioned this issue Jan 29, 2020
Closed
@Totktonada
Copy link
Member Author

BTW, it also wood be good to detect small temporary slowdowns. From point of view of an application developer, SLA, which (s)he can guarantee, lean on maximal possible latency, not average.

@kyukhin kyukhin added this to the 2.5.1 milestone Mar 6, 2020
@kyukhin kyukhin modified the milestones: 2.5.1, 2.6.1 Apr 10, 2020
@kyukhin kyukhin modified the milestones: 2.6.1, wishlist Oct 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
performance qa Issues related to tests or testing subsystem
Projects
None yet
Milestone
wishlist
Development

No branches or pull requests
2 participants
@Totktonada @kyukhin