# Jvm GC overhead
**URL:** https://discuss.elastic.co/t/jvm-gc-overhead/99139
**Category:** Elasticsearch
**Created:** [September 1, 2017, 2:10pm UTC](https://discuss.elastic.co/t/jvm-gc-overhead/99139 "2017-09-01T14:10:27Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Frederic\_Renan](https://discuss.elastic.co/u/Frederic_Renan)
#### Post date: [September 1, 2017, 2:10pm UTC](https://discuss.elastic.co/t/jvm-gc-overhead/99139/1 "2017-09-01T14:10:28Z")
Hi,
I've just start a new cluster with following specs :
Under VMWARE, dispatched on 2 datacenters :
2 data / master / ingest nodes : 16Go RAM / 8Go Heap / 4 vCPUs
2 master nodes : 8Go RAM / 2Go Heap / 2 vCPUs
With very few documents i'm starting to see GC overheap messages :
[2017-09-01T12:11:11,231][INFO][o.e.m.j.JvmGcMonitorService] [xxxxxxxxxxx] [gc][62272] overhead, spent [311ms] collecting in the last [1s]
the request is a simple discover over 2 days (2 indices) from kibana for approx. 400000 hits.
the heap is
I'm aware that GC troubles can't find a simple answer, but I'm very surprised to see them come very soon in my integration process.
What kind of measurements could be significant for this cluster ?
Is it a "classic" behaviour ?
Is there particularities around clusters on VMware VMs ?
---
### Author:  [@zqc0512](https://discuss.elastic.co/u/zqc0512)
#### Post date: [September 1, 2017, 2:31pm UTC](https://discuss.elastic.co/t/jvm-gc-overhead/99139/2 "2017-09-01T14:31:20Z")
use GCG1 not CMS try.
---
### Author:  [@Frederic\_Renan](https://discuss.elastic.co/u/Frederic_Renan)
#### Post date: [September 4, 2017, 8:58am UTC](https://discuss.elastic.co/t/jvm-gc-overhead/99139/3 "2017-09-04T08:58:33Z")
Not recommended by Elastic
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 2, 2017, 8:58am UTC](https://discuss.elastic.co/t/jvm-gc-overhead/99139/4 "2017-10-02T08:58:58Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.