fgprof VS pyroscope

As for OP: I'm not aware of a similar offering by AWS itself. You could try https://pyroscope.io/ but I'd be hesitant to recommend it because it's based (well, copied my code without attribution/license, different story : p) on my fgprof project. Unfortunately that means it won't scale to applications with many goroutines and add O(N) stop-the-world pauses to your application 🙈.

I agree the UI could use some work, but generally speaking CPU profiling is supported and does work. In fact, any HTTP endpoint that returns a valid pprof profile works, so even custom profiles are supported, such as fgprof.

What do you mean? pyroscope.io was slow for you? or the blog?

Tries (or prefix trees).

We use them a lot at Pyroscope for compressing strings that have common prefixes. They are also used in databases (e.g indexes in Mongo) or file formats (e.g debug symbols in macOS/iOS Mach-O format are compressed using tries).

We have an article with some animations that go into details about tries in case anyone's interested [0].

[0] https://github.com/pyroscope-io/pyroscope/blob/main/docs/sto...

You could use continuous profiling with Pyroscope which uses async-profiler under the hood, but with the added functionality that you can add relevant tags to your VMs (example).

Java Flight Recorder (JFR) is a format for collecting diagnostic and profiling data from Java applications. A while back someone created an issue for Pyroscope , an open source continuous profiler written in Go, to support ingesting profiles in JFR format, but there were no existing parsers that were also written in Go.

This cloud version is actually a slimmed-down version of Pyroscope which is open source and so you can run it locally.

At Pyroscope (open source continuous profiling) we use flamegraphs extensively to visualize and analyze profiling data. However, one of the worst parts about using flamegraphs for analysis is that they are kind of annoying to share.