[Lens] Find and implement generic solution to UI performance #77321
Labels
Feature:Lens
impact:medium
Addressing this issue will have a medium level of impact on the quality/strength of our product.
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
technical debt
Improvement of the software architecture and operational architecture
Projects
Comments
flash1293
added
technical debt
|
Pinging @elastic/kibana-app (Team:KibanaApp) |
stratoula
added
the
impact:medium
|
Closing as duplicate of #175485 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Due to the way Lens is structured updating the state can lead to frame drops while using the UI (e.g. typing in free text fields).
Currently this is fixed by debouncing the state update using the same patterns in multiple places, leading to very similar code in different places:
x-pack/plugins/lens/public/indexpattern_datasource/operations/definitions/filters/filter_popover.tsxx-pack/plugins/lens/public/indexpattern_datasource/dimension_panel/popover_editor.tsxx-pack/plugins/lens/public/pie_visualization/toolbar.tsxOne option to clean this up is to refactor the general "debounced state updater component" and use it in all places. However, maybe it's possible to improve performance by changing the scheme to apply state updates at the top level.
The text was updated successfully, but these errors were encountered: