# Any benefit using a node with 32GB heap & 96GB for OS+filesystem cache?

**URL:** <https://discuss.elastic.co/t/any-benefit-using-a-node-with-32gb-heap-96gb-for-os-filesystem-cache/218881>\
**Category:** Elasticsearch\
**Created:** [February 12, 2020, 2:15am UTC](https://discuss.elastic.co/t/any-benefit-using-a-node-with-32gb-heap-96gb-for-os-filesystem-cache/218881 "2020-02-12T02:15:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![linkerc](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@linkerc](https://discuss.elastic.co/u/linkerc)\
**Post date:** [February 12, 2020, 2:15am UTC](https://discuss.elastic.co/t/any-benefit-using-a-node-with-32gb-heap-96gb-for-os-filesystem-cache/218881/1 "2020-02-12T02:15:31Z")

</div>

I assume this type of node setting would benefit querying the same data over and over.  
But is there any down side to this in term of GC?  
Has anybody deploy nodes with much more RAM for FS than JVM?  
Anybody sharing his/her real experience would be highly appreciated.

Thanks.

---

<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:** [March 11, 2020, 2:15am UTC](https://discuss.elastic.co/t/any-benefit-using-a-node-with-32gb-heap-96gb-for-os-filesystem-cache/218881/2 "2020-03-11T02:15:36Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
