You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently I did many Profile-Guided Optimization (PGO) benchmarks on multiple projects (including many databases like PostrgreSQL, MongoDB, Redis, and many others) - the results are available here, all databases results are located here. So that's why I think it's worth trying to apply PGO to Proton as well.
I can suggest the following things to do:
Evaluate PGO's applicability and benchmark results to Proton.
If PGO helps to achieve better performance - add a note to Proton's documentation about that. In this case, users and maintainers will be aware of another optimization opportunity for Proton.
Provide PGO integration into the build scripts. It can help users and maintainers easily apply PGO for their own workloads.
Here are some PGO integration examples in the existing build scripts in other projects:
Hi!
Recently I did many Profile-Guided Optimization (PGO) benchmarks on multiple projects (including many databases like PostrgreSQL, MongoDB, Redis, and many others) - the results are available here, all databases results are located here. So that's why I think it's worth trying to apply PGO to Proton as well.
I can suggest the following things to do:
Here are some PGO integration examples in the existing build scripts in other projects:
configure
scriptSome PGO documentation examples:
After PGO, I can suggest evaluating LLVM BOLT as an additional optimization step after PGO.
The text was updated successfully, but these errors were encountered: