only now appreciating this wisdom
https://www.yosefk.com/blog/profiling-with-ctrl-c.html
=> More informations about this toot | More toots from tobinbaker@discuss.systems
@tobinbaker I just use a tool like eu-stack to dump the call stack of a process I am interested in. I just call it ten times in a row and if a function shows up multiple times, I take a look. That does not even take a minute. I do not even bother with a debugger.
=> More informations about this toot | More toots from andreaskem@hachyderm.io
@andreaskem this little tool automates that for you nicely: https://github.com/jasonrohrer/wallClockProfiler
=> More informations about this toot | More toots from tobinbaker@discuss.systems
@tobinbaker That is kind of cool but that almost looks like a proper profiler ;) I like the personal touch of doing "UpArrow", "Enter" a few times and then eyeballing the result. For something that requires a softer touch, there's still perf, at least on Linux.
=> More informations about this toot | More toots from andreaskem@hachyderm.io
@andreaskem Except that I still haven't found a way to tell perf to just sample all stacks whether on- or off-CPU. You can of course tell it to record scheduler events but that doesn't directly tell you how long an off-CPU stack was blocking.
=> More informations about this toot | More toots from tobinbaker@discuss.systems
@tobinbaker Yeah, I mostly need to figure out where CPU time is spent. You are probably aware of Brendan Gregg? If not, he writes about profiling on Linux. On his site, there is a perf example for off-CPU tracing but it is quite complicated. Nowadays, eBPF seems to be preferred for stuff like that:
https://www.brendangregg.com/blog/2015-02-26/linux-perf-off-cpu-flame-graph.html
https://www.brendangregg.com/offcpuanalysis.html
=> More informations about this toot | More toots from andreaskem@hachyderm.io This content has been proxied by September (3851b).Proxy Information
text/gemini