You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi guys, I'm using micrometer jmx registry to send metrics (specifically a timer) to JMX beans.
Profiling my application, I see that com.codahale.metrics.WeightedSnapshot$WeightedSample objects slowly increase without being garbage collected; is it normal? same for java.util.concurrent.ConcurrentSkipListMap$Node.
jmx-registry uses timer with default ExponentiallyDecayReservoir which it should be the most efficient in terms of memory consumption/GC; my test was stressing my app with 70req/s (the exact rate of my production app).
Any idea?
This discussion was converted from issue #3186 on February 17, 2023 22:54.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi guys, I'm using micrometer jmx registry to send metrics (specifically a timer) to JMX beans.
Profiling my application, I see that com.codahale.metrics.WeightedSnapshot$WeightedSample objects slowly increase without being garbage collected; is it normal? same for java.util.concurrent.ConcurrentSkipListMap$Node.
jmx-registry uses timer with default ExponentiallyDecayReservoir which it should be the most efficient in terms of memory consumption/GC; my test was stressing my app with 70req/s (the exact rate of my production app).
Any idea?
Thanks a lot
Alessandro
Beta Was this translation helpful? Give feedback.
All reactions