-
Notifications
You must be signed in to change notification settings - Fork 524
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PGO: optimize collected profile file size #14256
Conversation
This pull request does not have a backport label. Could you fix it @1pkg? 🙏
|
|
This pull request does not have a backport label. Could you fix it @1pkg? 🙏
|
|
This pull request does not have a backport label. Could you fix it @1pkg? 🙏
|
|
The result #14260 |
This pull request does not have a backport label. Could you fix it @1pkg? 🙏
|
|
(cherry picked from commit 3833927) # Conflicts: # .github/workflows/benchmarks.yml # systemtest/benchtest/profiles.go # testing/benchmark/Makefile
(cherry picked from commit 3833927) # Conflicts: # .github/workflows/benchmarks.yml # systemtest/benchtest/profiles.go # testing/benchmark/Makefile Co-authored-by: Kostiantyn Masliuk <[email protected]> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Motivation/summary
This PR addresses the issue #14255, by applying some quick optimization to how CPU profiles are collected for PGO. It reduces total collection time to 5% and strips unnecessary data such as tags and profile memory addresses that don't affect PGO.
Checklist
For functional changes, consider:
How to test these changes
Related issues
#14255
#13884