# Marvel high index rate

**URL:** https://discuss.elastic.co/t/marvel-high-index-rate/38935
**Category:** Elasticsearch
**Tags:** elastic-stack-monitoring
**Created:** [January 12, 2016, 5:01am UTC](https://discuss.elastic.co/t/marvel-high-index-rate/38935 "2016-01-12T05:01:47Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![tanguy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy/32/6030_2.png) [@tanguy](https://discuss.elastic.co/u/tanguy)
#### Post date: [January 12, 2016, 7:57pm UTC](https://discuss.elastic.co/t/marvel-high-index-rate/38935/4 "2016-01-12T19:57:27Z")

</div>

Marvel is indexing a set of documents for every nodes, indices and shards of your cluster. These documents are used to build the various charts.

In your case, you have many nodes / indices /shards compared to the volume of data (35 GB). That's around 100K / 80MB per index and this is not a lot.

Every 10 sec you have 11 (nodes) + 438 (indices) + 4348 (shards) = ~4800 documents indexed in 2 shards (marvel indices), so a total of 9600 docs every 10 secs which explains 960 docs /sec.

Hope this helps

---

_[View the full topic](https://discuss.elastic.co/t/marvel-high-index-rate/38935)._
