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

Measure performance overhead of tracing solution for Kibana server #102706

Closed
mshustov opened this issue Jun 21, 2021 · 4 comments · Fixed by #119932
Closed

Measure performance overhead of tracing solution for Kibana server #102706

mshustov opened this issue Jun 21, 2021 · 4 comments · Fixed by #119932
Labels
impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@mshustov
Copy link
Contributor

mshustov commented Jun 21, 2021 •
edited
Loading

Part of #101587
Before enabling the tracing solution by default for all the Kibana instances, we should test the defaults added in #102704 do not impact the overall Kibana performance.

For testing use the standard DemoJourney from https://github.com/elastic/kibana-load-testing
Compare numbers with execution_context.enabled: true and execution_context.enabled: false.
Based on the measurements, we should decide whether we can keep execution_context.enabled: true as the default or a Kibana user should opt-in to use it.

Note that the test the overhead for server-side only. The client-side logic is small enough to neglect its influence.
@mshustov mshustov added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Jun 21, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@mshustov mshustov mentioned this issue Jun 21, 2021
Closed
34 tasks
@mshustov mshustov mentioned this issue Jul 1, 2021
Merged
2 tasks
@mshustov mshustov changed the title Measure performance overhead of tracing solution Measure performance overhead of tracing solution for Kibana server Aug 4, 2021
@LeeDr
Copy link
Contributor

LeeDr commented Aug 4, 2021

@dmlemeshko is this a test you could do and report the results back here? Ideally by 7.15.0 FF.

@dmlemeshko
Copy link
Member

@LeeDr I think I should be able to run it on a Jenkins job with a small code change. I will double check with @mshustov

@dmlemeshko
Copy link
Member

dmlemeshko commented Aug 16, 2021 •
edited
Loading

Dedicated dashboard is created to represent test results.

Test Scenario: DemoJourney
Test runs: 3 each
Branch: master (cd3cc29) vs execution-ctx-disable (mshustov@5336d3e)
Load: ramping from 20 up to 800 concurrent users

Results: avg pefromance degradation is in 17-19% range with execution_context.enabled: true in place.

@mshustov mshustov mentioned this issue Aug 16, 2021
Merged
@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Nov 2, 2021
@mshustov mshustov mentioned this issue Nov 30, 2021
Merged
2 tasks
@exalate-issue-sync exalate-issue-sync bot added loe:medium Medium Level of Effort and removed loe:small Small Level of Effort labels Nov 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

enable execution_context by default mshustov/kibana
5 participants
@lukeelmers @mshustov @dmlemeshko @LeeDr @elasticmachine