# Large heap usage with each node

**URL:** https://discuss.elastic.co/t/large-heap-usage-with-each-node/969
**Category:** Elasticsearch
**Created:** [May 20, 2015, 2:22pm UTC](https://discuss.elastic.co/t/large-heap-usage-with-each-node/969 "2015-05-20T14:22:57Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![javadevmtl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javadevmtl/32/45613_2.png) [@javadevmtl](https://discuss.elastic.co/u/javadevmtl)
#### Post date: [May 24, 2015, 3:50pm UTC](https://discuss.elastic.co/t/large-heap-usage-with-each-node/969/13 "2015-05-24T15:50:31Z")

</div>

So now i'm at at 352 shards over 44 indexes and I still see 12GB of heap usage per node. I'm thinking the only way I can really reach passed 1 billion docs on the 4 nodes is to add extra node per physical machine since I have the horse power., But keep 4 shards + 1 replica config.

Btw i did some tests with my daily averages and I can even use single shard per index. But would that affect parallelism? I can also maybe provide yourkit snaphshot of what is eating up the ram...

---

_[View the full topic](https://discuss.elastic.co/t/large-heap-usage-with-each-node/969)._
