I run sentry self-hosted. I imagine there could be some additional consequences to this is in the hosted version but can be mitigated more in self-hosted (i.e. additional load and storage requirements for more precise profiles).

I have only tried profiling in a test environment with very low traffic (~30-50 samples) and I didn't find the aggregate flamegraphs useful because of the low resolution (and samples), but I will try generating more data and see how they work out.

I created an aggregate flamegraph with ~2,500 requests to the same page type (same template, different data) which you can see below alongside the flamegraph of (a single example) of the same page type.

You can pick out some of the larger function calls but lose a lot of the detail. For reference the function calls on the right hand side of the devtools flamegraph (t.a function call) are around 2.5-3ms and in our case are ones we could end up removing. These were not apparent in the aggregate flamegraph but were immediately suspicious in the devtools flamegraph. I spot checked a few individual flamegraphs in devtools and they all have a similar pattern (as expected) and aren't particularly close to the sentry aggregated flamegraph.

I am trying to optimize react SSR rendering here so there are many calls to fast function calls but the concerning part is the right hand side which is pretty much entirely missed in the aggregated flamegraph.