Continuous memory profiling #4498
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Motivation
jemallocis a more performant allocator (we do see a small performance improvement in benchmarks from it), and if we use it it's easier for us to have memory profiles.Proposal
This adds support for using
jemallocas an allocator, as well as expose a couple endpoints:Test Plan
Deployed a network with this and the
linera-infrachanges, saw the memory flamegraphs on Pyroscope, saw the memory profile Grafana dashboard, and managed to curl the flamegraph endpoint and get a memory profile svg returned to me.Release Plan