# Bulk Loading Performance slows to a crawl

**URL:** <https://discuss.elastic.co/t/bulk-loading-performance-slows-to-a-crawl/4867>\
**Category:** Elasticsearch\
**Created:** [July 14, 2011, 11:40pm UTC](https://discuss.elastic.co/t/bulk-loading-performance-slows-to-a-crawl/4867 "2011-07-14T23:40:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![derrickburns](https://avatars.discourse-cdn.com/v4/letter/d/50afbb/32.png) [@derrickburns](https://discuss.elastic.co/u/derrickburns)\
**Post date:** [July 14, 2011, 11:40pm UTC](https://discuss.elastic.co/t/bulk-loading-performance-slows-to-a-crawl/4867/1 "2011-07-14T23:40:29Z")

</div>

I am trying to index 80M tweets with a bulk loader that I wrote using  
the Java API on 0.16.4.

When I get to about 2M tweets, indexing performance drops from 4K  
indexed tweets per second to under 300 tweets per second. CPU load  
goes from 30% to 3%. Heap memory bounces between 300MB and 600Mb and  
then spikes to 900Mb.

Here are my index settings:

```
		index.engine.robin.refresh_interval, 10
		indices.memory.index_buffer_size, 0.50
 		index.number_of_shards, 4
		index.number_of_replicas, 0
		index.merge.policy.merge_factor, 30
		index.merge.policy.use_compound_file, false;
		index.refresh_interval, "-1"

```

I am doing this on a index I just created on a local node.

I am running on a new quad-core i7 Macbook Pro.

Ideas???

---

<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, 4:00am UTC](https://discuss.elastic.co/t/bulk-loading-performance-slows-to-a-crawl/4867/2 "2017-07-06T04:00:35Z")

</div>