It depends a bit on which collector you're using, but fairly normal. Heap grows for a while, then the JVM decides via a variety of metrics that it's time to run a collection. G1GC is usually a bit steadier and less sawtooth than the Parallel Mark Sweep , but if your heap's a lot bigger than needed I could see it producing that pattern.
On Thu, Jun 28, 2018 at 9:23 AM, Randy Lynn <rl...@getavail.com> wrote: > I have datadog monitoring JVM heap. > > Running 3.11.1. > 20GB heap > G1 for GC.. all the G1GC settings are out-of-the-box > > Does this look normal? > > https://drive.google.com/file/d/1hLMbG53DWv5zNKSY88BmI3Wd0ic_ > KQ07/view?usp=sharing > > I'm a C# .NET guy, so I have no idea if this is normal Java behavior. > > > > -- > Randy Lynn > rl...@getavail.com > > office: > 859.963.1616 <+1-859-963-1616> ext 202 > 163 East Main Street - Lexington, KY 40507 - USA > <https://maps.google.com/?q=163+East+Main+Street+-+Lexington,+KY+40507+-+USA&entry=gmail&source=g> > > <https://www.getavail.com/> getavail.com <https://www.getavail.com/> >
