# JVM old not populating

**URL:** <https://discuss.elastic.co/t/jvm-old-not-populating/85144>\
**Category:** Elasticsearch\
**Created:** [May 9, 2017, 5:39pm UTC](https://discuss.elastic.co/t/jvm-old-not-populating/85144 "2017-05-09T17:39:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dwjvaughan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dwjvaughan/32/10648_2.png) [@dwjvaughan](https://discuss.elastic.co/u/dwjvaughan)\
**Post date:** [May 9, 2017, 5:39pm UTC](https://discuss.elastic.co/t/jvm-old-not-populating/85144/1 "2017-05-09T17:39:06Z")

</div>

Currently running 5.3.2 on Centos 7 with the latest JDK. Heap set to 8GB on a 16GB VM.

Seem to have an issue where the JVM "old" pool is not being populated when I run a load test. I expect to see this increase when sending through around 80 searches a second but nothing. The JVM usage stays the same at around 800M. I'm concerned this is slowing down the searches as the JVM is always "cold".

Any help greatly appreciated!

---

<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:** [June 6, 2017, 5:46pm UTC](https://discuss.elastic.co/t/jvm-old-not-populating/85144/2 "2017-06-06T17:46:15Z")

</div>

Closed on June 6, 2017, 5:46pm UTC

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