Hacker News new | ask | show | jobs
by netingle 1188 days ago
Hi! Tom from Grafana Labs here, super excited to welcome the Pyroscope team and can’t wait to see what they achieve.

Continuous profiling is a next big thing IMO - easier to get started with than distributed tracing and delivers immediate value.
2 comments
anbotero 1188 days ago
I’m really, really liking this.

I’ve been testing the whole stack on a local server, finding kinks, documenting workflows, because I hope I move us to this soon. Now with Pyroscope I would love to try it out even more. I kid you not, we were just testing Datadog Continuous Profiling for our legacy Ruby application not two days ago and it was quite lackluster.

Not saying this will be better (have yet to try), but I’d prefer to support and report feedback back on this for a brighter future for our community.

Keep it up!

link
Rperry2174 1188 days ago
Ryan here from Pyroscope -- Awesome to hear you're interested in migrating over. Would love for you to try out our Ruby integration and let us know what you think: https://pyroscope.io/docs/ruby/.

We've added a lot of features like tags/labels, integration with tracing: https://github.com/pyroscope-io/otel-profiling-ruby, integration with CI/CD (in rails), etc.

Feedback very welcome!

link
felixge 1188 days ago
> we were just testing Datadog Continuous Profiling

Felix from Datadog here :). We'd love to hear your thoughts on our profiler if you're willing to share them. My e-mail is in my profile.

PS: Congrats to Ryan, Dmitry and team :).

link
anbotero 1186 days ago
Hey! It was alright, but at least for Ruby it didn’t report on the memory allocation of the calls, which is what we were looking for in the first place. We do not use it anywhere else, we only tried it for this pesky legacy system.
link
abuani 1188 days ago
This is exciting news Tom! Looking forward to seeing some posts in the future on how using Pyroscope reduced spend by finding perf improvements.
link