# Performance tuning for indexing between using dedicated coordinator code and using data nodes directly

**URL:** <https://discuss.elastic.co/t/performance-tuning-for-indexing-between-using-dedicated-coordinator-code-and-using-data-nodes-directly/197002>\
**Category:** Elasticsearch\
**Created:** [August 27, 2019, 8:46pm UTC](https://discuss.elastic.co/t/performance-tuning-for-indexing-between-using-dedicated-coordinator-code-and-using-data-nodes-directly/197002 "2019-08-27T20:46:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![yuecong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuecong/32/49061_2.png) [@yuecong](https://discuss.elastic.co/u/yuecong)\
**Post date:** [August 27, 2019, 8:46pm UTC](https://discuss.elastic.co/t/performance-tuning-for-indexing-between-using-dedicated-coordinator-code-and-using-data-nodes-directly/197002/1 "2019-08-27T20:46:25Z")

</div>

In my use case, I have a heavy load to index data continuously. I configured my data nodes with quite big CPU/Memory and using SSD. Also I have 3 dedicated coordinator nodes. At this point, both data read and write are through the coordinator nodes. I am wondering whether I should use data nodes directly when indexing node, but just use coordinator nodes for kibana to read data from. Could someone explain what the tradeoffs here I need to consider about?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 24, 2019, 8:46pm UTC](https://discuss.elastic.co/t/performance-tuning-for-indexing-between-using-dedicated-coordinator-code-and-using-data-nodes-directly/197002/2 "2019-09-24T20:46:25Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.