# Index throughput issues - tried all tuning suggestions posted

**URL:** https://discuss.elastic.co/t/index-throughput-issues-tried-all-tuning-suggestions-posted/19481
**Category:** Elasticsearch
**Created:** [August 27, 2014, 2:58am UTC](https://discuss.elastic.co/t/index-throughput-issues-tried-all-tuning-suggestions-posted/19481 "2014-08-27T02:58:27Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![pavan\_bkv](https://avatars.discourse-cdn.com/v4/letter/p/6a8cbe/32.png) [@pavan\_bkv](https://discuss.elastic.co/u/pavan_bkv)
#### Post date: [August 27, 2014, 2:58am UTC](https://discuss.elastic.co/t/index-throughput-issues-tried-all-tuning-suggestions-posted/19481/1 "2014-08-27T02:58:27Z")

</div>

Hi Kimchy. I have read quite a few posts from you on tuning the indexing in elastic search cluster for initial bulk loads. I have a 4 nodes cluster with 8G per node allocated to my elastic node (also these are VMs with centos and 4 core CPUs). I have tried increasing the shards, configuring the replications to 0, refresh interval to -1, index concurrency from 8 -16 and 32 and I use CB plugin to push data into ES cluster. Unfortunately what ever I do I still see a throughput of 2k records per second. I have 57 million docs to index (each 2k size with probably 200 fields per doc). At that rate it takes around 16-24 hours. But I want to cut this to 1-2 hours.

Please suggest me on how I can get this throughput. Appreciate any help regarding this.

---

<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: [July 6, 2017, 1:06am UTC](https://discuss.elastic.co/t/index-throughput-issues-tried-all-tuning-suggestions-posted/19481/2 "2017-07-06T01:06:09Z")

</div>


