# Would Coordinating nodes help with Kibana querying times **URL:** \ **Category:** Kibana\ **Created:** [August 21, 2019, 6:41pm UTC](https://discuss.elastic.co/t/would-coordinating-nodes-help-with-kibana-querying-times/196178 "2019-08-21T18:41:43Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![vchan2002](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vchan2002/32/46749_2.png) [@vchan2002](https://discuss.elastic.co/u/vchan2002)\ **Post date:** [August 21, 2019, 6:41pm UTC](https://discuss.elastic.co/t/would-coordinating-nodes-help-with-kibana-querying-times/196178/1 "2019-08-21T18:41:44Z")
I have some Kibana Dashboards, while they aren't necessarily used all the time, do require some very heavy queries (Each timelion dashboard with a heavy query X the number of visualizations on the dashbards)..... Right now, I have master only nodes and data only nodes. The data only nodes are fronted by an AWS ELB and Kibana points to that ELB. Would standing up Coordinating nodes and have Kibana point to coordinating nodes be a good idea in terms of offloading some of the aggregations compute from the data nodes? I could not find much documentation in regards to how much work is done on the searching/pulling data vs the aggregation part... just wondering whether that will help. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [August 21, 2019, 7:06pm UTC](https://discuss.elastic.co/t/would-coordinating-nodes-help-with-kibana-querying-times/196178/2 "2019-08-21T19:06:52Z")
Look at your data nodes and track CPU usage as well as disk I/O and iowait. That will give you an idea what might belimiting performance. If it is disk related, which is likely, I do not think dedicated coordinating only nodes will help much. ---
**Author:** ![amitavmohanty01](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/amitavmohanty01/32/58017_2.png) [@amitavmohanty01](https://discuss.elastic.co/u/amitavmohanty01)\ **Post date:** [August 21, 2019, 7:12pm UTC](https://discuss.elastic.co/t/would-coordinating-nodes-help-with-kibana-querying-times/196178/3 "2019-08-21T19:12:02Z")
I have tried using (master+data) setup where queries are directed to data nodes and a (master+data+coord) setup where queries are directed at coord nodes. The latter performs better. Of course if the bottleneck of the pipeline is somewhere else, as @Christian_Dahlqvist suggests, fix that first. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 18, 2019, 7:12pm UTC](https://discuss.elastic.co/t/would-coordinating-nodes-help-with-kibana-querying-times/196178/4 "2019-09-18T19:12:08Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.