K4's user experience is not as good as K3

[mkliu]

Despite all the new features, e.g. sub-aggregation and charting capabilities, our internal users still likes to use K3, simply becoz K3 is FASTER.

K4 tries to load everything back in one request, some of them, such as the "Searches" takes a long time to return. This long poll latency makes the entire page look slow.

Again, collapsible panels. I know the layout mechanism in K4 has changed, but the fact is It's hard to make complex dashboard in K4 now, only only does the page look clunky, but it also takes too long to load. We could of course create smaller dashboards, but people don't like to jump around links.

[rashidkpc]

There are a number of reasons to combine everything into an _msearch, but not the least of them is speed. In our testing K4's _msearch collecting of panel is significantly faster than making the requests in a serial(ish) fashion. This becomes even more apparent in larger dashboards

Definitely agree on collapsable panels. Ticket here: #1547 please add a comment!

[mkliu]

for _msearch test, how is the test conducted? Coz once we add a search panel, it's significantly slower. Nothing is showing up for quite a while.

The most often scenario is, I'm doing a slice&dice in the dashboard, once I'm satisfied with correct filters, then I deep dive into the docs in Search panel. But during slice&dice phase, i want to always wait for Search panel to return, time is wasted.

[flossokay]

I'm getting the same user experience here. Has there any news on this?