Kibana: Poor document table rendering performance
The current rendering of the document table takes several seconds for just 500 documents, which makes its use with larger datasets impractical.
:warning: The measurements and goals in this issue are a work in progress and will be expanded over time.
Progress
- [ ] measure current performance
- [ ] define performance targets
relates to elastic/kibana#10682
weltenwort
All 2 comments
In our use case the fetching of data is the most time consuming part of the rendering.
In an ideal case I think it should only fetch the first X records and fetch later on more records.
The first query should not include all possible records, but only the first 50 or so.
Elasticsearch does support continuing the search after the position of the last record (e.g. the 50th):
https://www.elastic.co/guide/en/elasticsearch/reference/master/search-request-search-after.html
foxylion
on 5 Jul 2017
Bargs
on 5 Jul 2017
Related issues
MaartenUreel
路
3Comments
socialmineruser1
路
3Comments
mark54g
路
3Comments
timroes
路
3Comments
stacey-gammon
路
3Comments
Most helpful comment
In our use case the fetching of data is the most time consuming part of the rendering.
In an ideal case I think it should only fetch the first X records and fetch later on more records.
The first query should not include all possible records, but only the first 50 or so.
Elasticsearch does support continuing the search after the position of the last record (e.g. the 50th):
https://www.elastic.co/guide/en/elasticsearch/reference/master/search-request-search-after.html