4 ms·
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 do
by brancz 3y ago
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 https://github.com/parca-dev/parca-agent
[2] https://www.parca.dev/ https://www.parca.dev/
- eyegor 3y agoIf 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 https://github.com/parca-dev/parca-agent/issues/161 Demo: https://github.com/parca-dev/parca-demo/pull/18 https://github.com/parca-dev/parca-demo/pull/18
- brancz 3y agoThanks for mentioning that! We'll do that. To clarify the current state: dotnet and jvm require enabling flags, python fully works without any changes (as of 2 weeks ago blog post on how we made this possible is about to be released).