3 ms·
Curious, how does this compare with Datadog's offering? https://docs.datadoghq.com/tracing/profiler/ https://docs.datadoghq.com/tracing/profiler/
by kveykva 6y ago
Curious, how does this compare with Datadog's offering?
https://docs.datadoghq.com/tracing/profiler/ https://docs.datadoghq.com/tracing/profiler/
- petethepig 6y agoThe way we see it right now Pyroscope pros: * it's open source, you can use it locally, or deploy it in your infra * our timeline UI is more intuitive imo, e.g you can easily zoom in on particular time ranges you're interested in, you can try it on our demo page: https://demo.pyroscope.io/?name=hotrod.golang.customer%7B%7D&from=now-6h https://demo.pyroscope.io/?name=hotrod.golang.customer%7B%7D... * it's gonna be cheaper to run in most cases * we have Ruby support Pyroscope cons: * no support for tags right now. There is support for this in the storage engine, but we need to wire the UI and integrations to take advantage of it * no Java support yet * no support for memory / IO profiling yet, just CPU