# Kibana data table visualization is too slow in response **URL:** \ **Category:** Kibana\ **Created:** [September 14, 2017, 8:41pm UTC](https://discuss.elastic.co/t/kibana-data-table-visualization-is-too-slow-in-response/100605 "2017-09-14T20:41:45Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![rajkamalkool6](https://avatars.discourse-cdn.com/v4/letter/r/e9c0ed/32.png) [@rajkamalkool6](https://discuss.elastic.co/u/rajkamalkool6)\ **Post date:** [September 14, 2017, 8:41pm UTC](https://discuss.elastic.co/t/kibana-data-table-visualization-is-too-slow-in-response/100605/1 "2017-09-14T20:41:45Z")
I have 5 node Elasticsearch cluster 3 master node 1 data node and 1 Tribe node. I have installed `ELK 5.2` version. My shards count is 2 and replica is 1. I have `32GB RAM and 1TB of hard disk space`. My Index size is around `14GB`. I have configured my kibana.yml to point both the tribe and master node > elasticsearch.tribe.url: "[http://xxxx:9200](http://xxxx:9200)" > > elasticsearch.url: "[http://xxxxx:9200](http://xxxxx:9200)" Whenever I created a data-table visualization with date datatype as one of the column my search becoming too slow sometimes I am getting `timeout error`. When I remove the date type column form the visualization the search is better. ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/e/be196fb36e31ee2753151020997c1e9fd0d4bb75.png) Is there any setting which I need to add in the config file or need to modify any Elasticsearch mapping. Please advice me the configuration to overcome the issue. ---
**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\ **Post date:** [September 14, 2017, 8:45pm UTC](https://discuss.elastic.co/t/kibana-data-table-visualization-is-too-slow-in-response/100605/2 "2017-09-14T20:45:50Z")
Why are you doing a `terms` aggregation on a `Date` field? Your terms aggregation is asking for a very large number of terms. Using a `Date Histogram` aggregation will fix your performance problems. ---
**Author:** ![rajkamalkool6](https://avatars.discourse-cdn.com/v4/letter/r/e9c0ed/32.png) [@rajkamalkool6](https://discuss.elastic.co/u/rajkamalkool6)\ **Post date:** [September 14, 2017, 9:37pm UTC](https://discuss.elastic.co/t/kibana-data-table-visualization-is-too-slow-in-response/100605/3 "2017-09-14T21:37:57Z")
@Nathan_Reese When I use `Date Histogram` Yes its too faster but I couldn't see the minutes, sec and milliseconds information. ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/d/7dbf76fb01b914d81a38e19c1b05b0c1e117b172.png) ---
**Author:** ![Nathan\_Reese](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathan_reese/32/84829_2.png) [@Nathan\_Reese](https://discuss.elastic.co/u/Nathan_Reese)\ **Post date:** [September 14, 2017, 9:57pm UTC](https://discuss.elastic.co/t/kibana-data-table-visualization-is-too-slow-in-response/100605/4 "2017-09-14T21:57:17Z")
Why are you sub-aggregating the date histogram bucket with a terms aggregation on the same date field? Can you describe your use case and data set so I can get a better understanding of what you are trying to accomplish. ---
**Author:** ![rajkamalkool6](https://avatars.discourse-cdn.com/v4/letter/r/e9c0ed/32.png) [@rajkamalkool6](https://discuss.elastic.co/u/rajkamalkool6)\ **Post date:** [September 15, 2017, 1:01pm UTC](https://discuss.elastic.co/t/kibana-data-table-visualization-is-too-slow-in-response/100605/5 "2017-09-15T13:01:03Z")
Just to show you the difference I created this same field. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 13, 2017, 1:01pm UTC](https://discuss.elastic.co/t/kibana-data-table-visualization-is-too-slow-in-response/100605/6 "2017-10-13T13:01:49Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.