Reported GC time is way too high

Skip to first unread message

Eax Melanhovich

Dec 22, 2014, 8:24:35 AM12/22/14

I'm using Kamon with Datadog. Here is how one of the charts looks like:

Which units are these? I doubt that this is milliseconds, since if I had
such GC time, I would notice :) It's also doubtful that we are talking
about microseconds.

I took a look at


Although the code is quite complicated it looks like unit should be

Could it be a bug? Or maybe I'm doing something wrong?

Best regards,
Eax Melanhovich

Ivan Topolnjak

Dec 22, 2014, 10:46:26 AM12/22/14
Hello Eax, welcome to our community!

The time you are seeing is indeed in milliseconds and I guess that the reason for being so high is that it is the accumulated [1] time since the startup of your JVM. Probably if you zoom out to hours or even days depending on how long it has been running, you should see "normal" collection times of few milliseconds and ramping up over the lifetime of the JVM running the app.

Now that I think about it, it would be nice to report the difference in GC time since the last tick, instead of the accumulated value that it is reporting now. It should be a lot easier to identify longs stalls related to GC by doing it that way as well as identifying when the GCs happen. What do you think about that change?

Eax Melanhovich

Dec 22, 2014, 10:55:43 AM12/22/14
to Ivan Topolnjak,
Sounds reasonable. In fact, accumulated value was last thing I
expected :)

Diego Parra

Dec 27, 2014, 2:54:38 PM12/27/14
Hi Eax,  

just in case that you want follow this problem, we open a new issue [1]

You received this message because you are subscribed to the Google Groups "kamon-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
For more options, visit

Eax Melanhovich

Dec 29, 2014, 2:46:21 AM12/29/14
to Diego Parra,
Thank you!
Reply all
Reply to author
0 new messages