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

[Lens] Identify and fix performance bottlenecks with large index patterns #77898

Closed
mbondyra opened this issue Sep 18, 2020 · 5 comments
Closed
Labels
bug Fixes for quality problems that affect the customer experience Feature:Lens performance Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@mbondyra
Copy link
Contributor

The goal of this issue is to gather the circumstances of where Lens becomes too slow to being used comfortably.
This issue is created to track these situations, decide what to do with them, fix them and find a strategy to make the fixes sustainable (eg performance testing).

Known cases:

  • loading big index patterns like filebeat-* (more than 4000 fields)
@mbondyra mbondyra added performance technical debt Improvement of the software architecture and operational architecture Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens labels Sep 18, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@wylieconlon
Copy link
Contributor

Updating the title because there is only one example

@wylieconlon wylieconlon changed the title [Lens] Identify and fix performance bottlenecks [Lens] Identify and fix performance bottlenecks with large index patterns Sep 18, 2020
@flash1293 flash1293 added bug Fixes for quality problems that affect the customer experience and removed technical debt Improvement of the software architecture and operational architecture labels Sep 21, 2020
@flash1293
Copy link
Contributor

Performance levels should be back to 7.8 levels by #77210 but I think it still makes sense to keep this issue open because it looks like there is still room for improvement. I will move it back to minor bugs though because in most scenarios performance should be acceptable now.

@flash1293
Copy link
Contributor

@mbondyra Reconsidering my stance from last September - is there something we can do right now? If there's not specific plan I would like to close this issue until we come up with concrete steps.

@mbondyra
Copy link
Contributor Author

Makes sense. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Lens performance Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

No branches or pull requests

4 participants