# Indexing performance degrading over time

**URL:** https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229
**Category:** Elasticsearch
**Created:** [January 27, 2016, 12:30pm UTC](https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229 "2016-01-27T12:30:27Z")
**Posts on this page:** 1
**Showing post:** 16

<div class="post-metadata">

### Author: ![mikemccand](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@mikemccand](https://discuss.elastic.co/u/mikemccand)
#### Post date: [February 2, 2016, 10:36am UTC](https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229/16 "2016-02-02T10:36:56Z")

</div>

That's odd that you only see the slow down when indexing with nested documents.

Nested documents do require more work to index and merge, since under-the-hood, each of your 1 to 3 nested docs (plus the parent doc) are indexed as separate documents to Lucene, but that work should not be increasing over time.

Can you pull a full hot threads (pass e.g. threads=10000 to [https://www.elastic.co/guide/en/elasticsearch/reference/2.1/cluster-nodes-hot-threads.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.1/cluster-nodes-hot-threads.html)) from all nodes when things have gotten very slow with the nested documents?

---

_[View the full topic](https://discuss.elastic.co/t/indexing-performance-degrading-over-time/40229)._