/ go Public
cmd/compile: reduce PGO profile processing overhead #58102
Issues related to the Go compiler and/or runtime.
The path to resolution is known, but the work has not been done.
Currently, each cmd/compile invocation parses the full PGO pprof profile, builds a full weight graph, and then determines what is relevant to that package. This is a lot of work that scales poorly with the size of the profile and the size of the build (number of packages). For particularly large profiles, this can lead to extremely long build times.
Follow-up to #55022.
cc @cherrymui @aclements
The text was updated successfully, but these errors were encountered: