Kibana 4.*.* is very slow (also crashes browser) possibly due to the lack of pagination in query results

[blacktop]

I am using ES to store many millions of deeply nested json docs. I want to use Kibana to query and display it, however, due to the fact that in 4 there is not pagination of the results. My queries return MANY docs that are being held in memory by Kibana causing the site to become very sluggish and almost unusable. I think if you added pagination this would fix the issue as performing the same queries via a command line return results almost instantaneously. My ES cluster consists of 1 load balancer node, 3 Master nodes (2 are backup masters) and 20 data nodes. All of which are m1.large instances.

Thanks.

[rashidkpc]

Grab a snapshot build, we removed the tracking of response history which should reduce long term memory usage by 20x in some cases. That said, it sounds like you might have very large mappings, which is more likely to be the problem, see this ticket:

#1540

[blacktop]

I am using the nightly build. Also it is not the kibana index selection screen that is crashing the browser. It's Kibana not paginating the results from a query. Why do you not paginate like in Kibana 3 and Splunk?

[eamonngryan]

Is there any other update on this issue? We are experiencing the same issue where our Kibana query is returning a lot of data in a data table visualization and because there is no pagination of the results it tries to load everything and it takes a long time for the dashboard to load. It isn't clear whether #1540 will address this problem.