cmd/trace: analyze Go 1.22+ traces scalably #65315
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
FeatureRequest
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Currently cmd/trace loads the entire expanded trace into memory, always. However, the Go 1.22+ trace API is a streaming API, so it's totally possible for the tool to split up traces and only touch the necessary parts.
This will require some refactoring, and will definitely be easier once we remove the old tracer and the old tracer parser (putting old trace parsing behind the new API in internal/trace/v2).
The text was updated successfully, but these errors were encountered: