Table Panel slows down browser with large number of fields #719
Comments
|
Out of curiosity - 2700 fields? What sort of data are you looking at with Kibana? |
|
Heh, I suppose I should start making separated indexes for this stuff. Right now I'm throwing a lot of product eventing data into this. (Which can be crazy.) In addition all Load Balancer logs etc. (We're a big property...) The main issue is probably the fact that Kibana doesn't support nested JSON the way I want, so I flatten my nested JSON which creates A LOT more fields. See #677 as to why I'm flattening my JSON. |
|
My gut feeling is that this is related to autocomplete, and if I can turn that off, that'd be great. |
|
this is caused when Kibana tries to determine the available fields in the table. It does this by looping over the events and extracting the keys. With 2700 fields, and 100 rows in the table we're talking 270,000 keys to extract. I've been trying to figure out a more efficient way since even with 200 or so fields there's a lot of overhead to that process. |
|
Also another idea I just had could be to perform some work (such as counting and flattening) inside a webworker. The huge advantage is that webworkers perform their work outside the main run loop and are not "supposed" to slow down the browser GUI. Also it's possible to pass some data to these object quite quickly in some conditions... |
* master: Moved doc task to the end of the default task chain removed y_as_bytes, replaced with y_format Remove console.log Closes elastic#538. Closes elastic#722 Potential fix for elastic#621 More small table performance improvements Improve performance in the table. Re elastic#719 and elastic#732 Remove idQueue from filter and query services in dashboards Eliminate idQueue property from filterSrv and querySrv. Replace with binary search for smallest id. Closes elastic#730. Closes elastic#739 Skeleton API docs Doc updates Added scratchy tasks and config.js docs Bytes should not be default Fixing unsafe html binding fixed numeric terms in topN query do not auto-enable saved filters
|
I stil see the problem with 15097 fields. Is there a way to filter the unwanted fields? |
|
related issue: |
|
Judging by the date when this was filed, I believe this issue is related to Kibana 3 table panel. Refer to the following issue dealing with displaying large number of fields in a document table in Kibana 4: #6328 |
and others
Hello,
Here's another request. The Table Panel slows down my browser considerably now that I have a large number of fields. (I have around 2700 fields!)
I think it might have something to do with autocomplete? Not sure. But it's making my Kibana dashboards almost unusable. :-(
Any pointers here?
Thanks,
-Bryan
The text was updated successfully, but these errors were encountered: