Skip to content
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

Apply PGO to the AutoFDO itself #170

Open
zamazan4ik opened this issue Jun 17, 2023 · 3 comments
Open

Apply PGO to the AutoFDO itself #170

zamazan4ik opened this issue Jun 17, 2023 · 3 comments

Comments

@zamazan4ik
Copy link

Did anyone try to apply PGO (or AutoFDO - whatever) to AutoFDO binaries themselves? It could help with improving performance a little since AutoFDO works quite a long on huge profiles. Saving several percent would be appreciated for the users who run AutoFDO as a part of a regular CI.

If you already have some results and can share them - would be awesome to see!

@shenhanc78
Copy link
Collaborator

The beliefe here is that PGO on top of AutoFDO would beat PGO alone.
Also AutoFDO on top of AutoFDO is an iterate action, that can be done repeatedly, we have had experiments showing that by doing this, performance goes up and down, it's not always a win.

@zamazan4ik
Copy link
Author

No. I mean not applying PGO after AutoFDO. I mean applying PGO on AutoFDO tools (create_gcov, profile_merger, etc).

@shenhanc78
Copy link
Collaborator

I see. That makes sense, if the time running AutoFDO tools is not a negligible portion of the whole build time. For large projects, the compile / link time is predominant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants