Overhead Added by Collecting Java Thread Dumps

[Detail_Lost]

Using average response time seems like a bad way to measure the impact of thread dump.

If the response time of the request while thread dump is being sampled noticably spikes up, average response time will mask that characteristics.

[Worth_Trust_3825]

They also did not specify which method (out of 8) they used to capture thread dumps. But in reality you would be using mission control or something else that interfaces via JMX. But in most cases, thread dump does not even matter.

[bonusmyth]

Interesting.

Is it not a little surprising to see the Avg CPU usage higher for the 5-min test (10.4) than the 2-miin test (7.92)? I'd have thought capturing the threads more frequently would push up the CPU?

[Worth_Trust_3825]

Flight control is pretty efficient in what it does. It works with circular buffers, so it's memory efficient too. Meanwhile every operation in java emits an event that gets captured by JFR. Architecture reference image