Re:Profiling Go Applications with Flamegraphs
by LaFolle on Monday March 12, 2018 @01:40AM
(#16566388)
One way to solve this I can think of is, if cpu spikes are deterministic, then we can take 2 profiles:
1. span consisting of no spikes
2. span consisting of at least 1 spike
And then "diff" them to get stack causing spikes.
Is this the correct way?
In general, how do people solve CPU spikes issue?
But do they help to debug issues related to CPU spikes? I have my reservations because they are generated using sampling, and flamegraphs won't give a clear insight into who is causing the spikes.