# Spikes in Indexing Rate - Methods to Increase Indexing Rate?

**URL:** <https://discuss.elastic.co/t/spikes-in-indexing-rate-methods-to-increase-indexing-rate/68740>\
**Category:** Elasticsearch\
**Created:** [December 12, 2016, 4:58pm UTC](https://discuss.elastic.co/t/spikes-in-indexing-rate-methods-to-increase-indexing-rate/68740 "2016-12-12T16:58:09Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [December 13, 2016, 8:17pm UTC](https://discuss.elastic.co/t/spikes-in-indexing-rate-methods-to-increase-indexing-rate/68740/4 "2016-12-13T20:17:54Z")

</div>

> [@seth.yes](#):
>
> Do you mean 'send requests to the master or client nodes'? I'm curious if there's a logical preference between the two..

Sorry, I meant "send requests to the data and client nodes, not the master nodes".

> [@seth.yes](#):
>
> Also, I've read that having too many client nodes can be detrimental to performance as any data allocation process by one client node must be confirmed with the other before data is committed.

Where did you read this?

> [@seth.yes](#):
>
> The load doesn't seem too large, the master & data nodes all have 24 CPUs, the VMs each have 8.

Yeah that looks ok.

---

_[View the full topic](https://discuss.elastic.co/t/spikes-in-indexing-rate-methods-to-increase-indexing-rate/68740)._