Where do you position yourself compared to Pyroscope? #14
-
Continuous profiling isn't new, e.g. there is already a wildly popular and production ready Grafana Pyroscope that can profile not just CPU, but memory, allocations, locks etc How do you compare yourself to Pyroscope and why should the community use Perforator? What new ideas does it bring? What problems does it solve that Pyroscope doesnt? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Great question! Perforator indeed looks similar to Pyroscope. However, we think that the closest existing solutions are https://parca.dev, closed-source Google Wide Profiling, and, speaking of the agent, the beautiful OpenTelemetry eBPF profiler. The main technical differences with Pyroscope we see are:
In summary, we try to implement native profiling almost perfectly. It's worth noting that Pyroscope is a mature, well-established product that integrates excellently with the Grafana ecosystem. We have just focused on different things: our focus has been on optimizing native code profiling and making it as accurate and low-overhead as possible. |
Beta Was this translation helpful? Give feedback.
Great question! Perforator indeed looks similar to Pyroscope. However, we think that the closest existing solutions are https://parca.dev, closed-source Google Wide Profiling, and, speaking of the agent, the beautiful OpenTelemetry eBPF profiler. The main technical differences with Pyroscope we see are: