Increase Kibana responsiveness

[alepuccetti]

Describe the feature:

When you have many visualizations (especially using aggregations) in a dashboard the loading time could get very high. Kibana uses a single _msearch to return all the queries results this bounds the return time to the slowest query.

Few ideas:

1. Introducing loading bar per visualization.
2. Cap the number of visualizations resolved in one _msearch and have multiple calls of _msearch.
   2.2 To the extreme: one query per visualization (this may impact Elasticsearch performances?).
3. Enable Kibana to fire queries only of the visible visualizations.

[shaharmor]

@alepuccetti the new TSVB visualization already does 1 request per visualization

[alepuccetti]

@shaharmor Good to know but what about the other visualizations? If you have a dashboard with visualizations (not TSVB or timelion) the dashboard view do a single _msearch to for all of them bounding the response to the slowest one. Also, point 3 will improve user experiences and could be even that Kibana will query all the vis but wait for the visible one to finish before querying the others. Example of the flow:

1. Query all the visible visualizations one query per visualization.
2. Wait for the last (or first) to return.
3. Start query the first not-visible visualization.

In this scenario, having a loading bar per visualization will be useful to see which visualization returned an which did not. Also, the user could start looking to some of the data while other visualizations load.

A possible side effect is that: If the date format use now, data between visualizations could represent slight different timeframe.

[epixa]

@stacey-gammon Is there already an issue for more robust handling of dashboard searches? I could have sworn there was, but I can't find it.

[stacey-gammon]

Ah yep, I filed #14750 shortly after this one was filed.

[epixa]

@alepuccetti Thanks for opening this issue. While #14750 is newer than this, I'm going to close this issue in favor of that one since there is some more discussion going on in that other issue.