# Indexing2

**URL:** <https://discuss.elastic.co/t/indexing2/57537>\
**Category:** Elasticsearch\
**Created:** [August 8, 2016, 11:32pm UTC](https://discuss.elastic.co/t/indexing2/57537 "2016-08-08T23:32:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jspooner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jspooner/32/12984_2.png) [@jspooner](https://discuss.elastic.co/u/jspooner)\
**Post date:** [August 8, 2016, 11:32pm UTC](https://discuss.elastic.co/t/indexing2/57537/1 "2016-08-08T23:32:43Z")

</div>

Indexing234

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [August 9, 2016, 2:52am UTC](https://discuss.elastic.co/t/indexing2/57537/2 "2016-08-09T02:52:48Z")

</div>

Sure. Exactly the performance you get depends on a lot of things, but the  
first few things to try are to use the \_bulk API to load your documents and  
to set the refresh interval to -1. To optimize the size of the bulk request  
measure loading speed at a couple of mb per bulk and then increase it and  
remeasure. Stop when it doesn't improve speed anymore or when you get to 20  
or 30 mb. Those are fairly large bulks.

SSDs are much faster to write to, don't be afraid to use raid 0 and let  
elasticsearch handle the redundancy. It is fairly normal to load with 0  
replicas and then add them after load. It depends on your tolerance for  
failure.

---

<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 5, 2017, 10:29pm UTC](https://discuss.elastic.co/t/indexing2/57537/3 "2017-07-05T22:29:11Z")

</div>

Closed on July 5, 2017, 10:29pm UTC