[Meta][Lens] Performance

[flash1293]

The perceived performance of the Lens editor is important for a pleasant user experience. This issue tracks various potential enhancements and common pitfalls for poor performance.

Issues

• [Lens] Support Sampler & Diversified Sampler aggregations #120788

  • what features should always use sampled? Suggestions is top of our mind here
  • popover in field list at some point?
  • suggestions powered by sampler?

• [Lens] Performance problems of text inputs that modify state in Dimension Panel #77167

• [Lens] Avoid index pattern remapping for each visualization #89269

• [Lens] Bail out of suggestion rendering if load times are too long #100345

• [Lens] Unnecessary data reload after saving Lens as new #104790

• [Lens] Omit "over time" suggestion for expensive configurations #112229

• [Lens] Render suggestions after main chart #100346

• [Lens] Allow users to not render suggestions #85518

• Visualization collectors iterate over all visualizations 4 times #117367

• Do not fetch full visualization SO when visiting listing page #118144

• [Lens] Make "auto-apply" behavior configurable #74490

• [Lens] Optimize percentiles fetching #126941

• [Lens] Return 'other' bucket in a single request for counts #135211

• TSVB: Improve performance / lag when interacting with a large number of series #14799

• Don't send runtime field mappings when the field is not in use #139025

• Disable Kibana Auto Form Submit #29356

• [Lens] prompt user when editor performance is impacted #158321

• [Lens] Turn off Group remaining values as "Other" setting when visualization has more than 1000 terms aggregation #162456

• Cost of the embeddable in terms of time/memory/processing overhead (@markov00)

• Layers with multiple timeshifts [AggConfigs] Optimize time shift data fetching for same aggregation #132583

• [EsAggs] Improve agg performance setting track_total_hits to false #164194

Issues watching (other plugins/teams)

• [Lens] bsearch not aborted after changing the layers #123030
• Optimize sibling aggs together elasticsearch#82373

Features that diminish query performance

Features to design solutions and recommendations for. Link issues / info as appropriate.

• high # of buckets (date_histogram with nested terms specifically can drive this)
  • [Lens] Expose shard size for top values (terms) aggregations #117909
• use of runtime fields (are all runtime field equally bad?)
• lots of filter aggregations
• use of multi_terms (once added) - "25% slower in Joe's anecdotal tests"
  • We are holding on implementing more routes to multi terms to measure performance in its initial release [Lens] XY - Dragging a 2nd+ text field to workspace creates multi field #123414

Features that diminish accessibility & usability performance

• Contrast checking

Telemetry we could use

• Collect performance of query in visualization plugin
• Query-To-Render time: how much time a query would take from being started by Lens and being rendered on the screen (should include: Request/Response Time, processing time, rendering time). Will serve to determine bottlenecks and compare our times to process the data to the ES query time. Could be telemetry, but will be easily just to have it a simple local benchmark (@markov00)

Dependent issues

• Optimize request fetching for filters and filter aggs #136796

[elasticmachine]

Pinging @elastic/kibana-vis-editors (Team:VisEditors)

[timductive]

Closing old meta issues in favor of more granular, current meta issues