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] Cache field existence requests #104060

Closed
flash1293 opened this issue Jul 1, 2021 · 3 comments
Closed

[Lens] Cache field existence requests #104060

flash1293 opened this issue Jul 1, 2021 · 3 comments
Labels
enhancement New value added to drive a business result Feature:Lens performance Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@flash1293
Copy link
Contributor

Thanks to the client side request cache which is part of the search service, requests for main chart and suggestions are cached when going back and forth between Lens and Dashboard.

However before Lens becomes usable, the field list has to render which blocks on the field existence request. This request is often pretty fast, but depending on the system it can take up to 5 seconds which can be a significant amount of time until the UI becomes usable.

We should apply a similar caching bound to the current session id for these requests to speed up the user flow.

@flash1293 flash1293 added performance enhancement New value added to drive a business result Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens labels Jul 1, 2021
@elasticmachine
Copy link
Contributor

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

@flash1293
Copy link
Contributor Author

Related to #74493

@flash1293
Copy link
Contributor Author

This isn't necessary anymore on the Lens side once #112782 is implemented

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Lens performance Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

No branches or pull requests

2 participants