11–19 of 19 posts
What format does this support? Would be nice to have more examples, like how do I connect this to node profiling for instance?
URL in example says Go pprof so at least that. I wish it to be compatible with my go-to Ruby tools: https://github.com/ruby-prof/ruby-prof https://github.com/rbspy/rbspy thus replacing this one: https://github.com/brendangregg/FlameGraph
What format does this support? Would be nice to have more examples, like how do I connect this to node profiling for instance?
For now, golang only. But I am working on other supports. Is there any common format for flamegraph (stacks), or should I do the work for all tools and languages?
https://www.brendangregg.com/flamegraphs.html
So if you can make your tool eat whatever https://github.com/brendangregg/FlameGraph is fed with you're going to support a lot of existing tooling across OSes and languages.
Earlier quoted context omitted.
Since pprof is supported you could use parca-agent [1], an eBPF-based profiler that I happen to work on, as when you browse the debug UI on port 7071 you can download a pprof formatted profile for any process running on the machine. Supports Go, Rust, C++, C, Ruby, Python, C#, Java, Julia, Erlang, Nodejs, wasmtime, and more. [1] https://github.com/parca-dev/parca-agent [2] https://www.parca.dev/
If that's true, you should probably update the docs. Everything I could find implied dotnet, jvm, python were still unsupported. For example, the roadmap section of the readme mentions most of these as future targets but nothing even mentions dotnet. However I did find your tickets and a demo being merged in which makes dotnet seem maybe supported? Ticket: https://github.com/parca-dev/parca-agent/issues/161 Demo: htt…
What format does this support? Would be nice to have more examples, like how do I connect this to node profiling for instance?
For now, golang only. But I am working on other supports. Is there any common format for flamegraph (stacks), or should I do the work for all tools and languages?
There appears to be zero documentation on what it needs as input.
this is very cool, but...where does one get the data to visualize? Is there a standard for flamegraph data structures? There appears to be zero documentation on what it needs as input.
this is very cool, but...where does one get the data to visualize? Is there a standard for flamegraph data structures? There appears to be zero documentation on what it needs as input.
> Currently it only supports Golang's pprof dump, I am working on supporting more formats
this is very cool, but...where does one get the data to visualize? Is there a standard for flamegraph data structures? There appears to be zero documentation on what it needs as input.
I already figure out how to integrate with golang's pprof, seems I need to work with other perf tools as well.
I am thinking about adding a flag like `--input-format=pprof` for different outputs.