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

Evaluate using Profile-Guided Optimization (PGO) and Post-Link Optimization (PLO) on ctags #3849

Open
zamazan4ik opened this issue Nov 18, 2023 · 1 comment

Comments

@zamazan4ik
Copy link

Hi!

Recently I checked Profile-Guided Optimization (PGO) improvements on multiple projects. The results are available here. I also have several examples of applying PGO to the software like ctags:

That's why I think trying to optimize ctags with PGO can be a good idea.

I can suggest the following action points:

  • Perform PGO benchmarks on ctags. And if it shows improvements - add a note to the documentation about possible improvements in ctags performance with PGO.
  • Providing an easier way (e.g. an additional build option) to build scripts with PGO can be helpful for the end-users and maintainers since they will be able to optimize ctags according to their workloads.
  • Optimize pre-built binaries (if it's possible to prepare a good training workload)

Testing Post-Link Optimization techniques (like LLVM BOLT) would be interesting too (Clang and Rustc already use BOLT as an addition to PGO) but I recommend starting from the usual PGO.

Here are some examples of how PGO optimization is integrated in other projects:

@masatake
Copy link
Member

Thank you for this input.

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