# What's eating node's memory? **URL:** https://discuss.elastic.co/t/whats-eating-nodes-memory/35366 **Category:** Elasticsearch **Created:** [November 23, 2015, 10:14pm UTC](https://discuss.elastic.co/t/whats-eating-nodes-memory/35366 "2015-11-23T22:14:41Z") **Posts on this page:** 1 **Showing post:** 6
### Author: ![michaelr524](https://avatars.discourse-cdn.com/v4/letter/m/7cd45c/32.png) [@michaelr524](https://discuss.elastic.co/u/michaelr524) #### Post date: [November 24, 2015, 6:53am UTC](https://discuss.elastic.co/t/whats-eating-nodes-memory/35366/6 "2015-11-24T06:53:04Z")
This seems like a similar problem: > [@Large heap usage with each node](https://discuss.elastic.co/t/large-heap-usage-with-each-node/969/13): > > 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/whats-eating-nodes-memory/35366)._