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 (network-related projects like Envoy, HAProxy, etc.) - the results are available here. I think it could interesting to try to test PGO for optimizing the CPU part of NFSserve.
I can suggest the following things to do:
Evaluate PGO's applicability to NFSserve.
If PGO helps to achieve better performance - add a note to NFSserve's documentation about that. In this case, users and maintainers will be aware of another optimization opportunity for NFSserve.
Provide PGO integration into the build scripts. It can help users and maintainers easily apply PGO for their own workloads.
Here are some examples of how PGO is already integrated into other projects' build scripts:
@ylow I guess you can leave the issue open. So if anyone from the community will be interested in work on this task - the issue will be already open for them.
Hi!
Recently I did many Profile-Guided Optimization (PGO) benchmarks on multiple projects (network-related projects like Envoy, HAProxy, etc.) - the results are available here. I think it could interesting to try to test PGO for optimizing the CPU part of NFSserve.
I can suggest the following things to do:
Here are some examples of how PGO is already integrated into other projects' build scripts:
configure
scriptAfter PGO, I can suggest evaluating LLVM BOLT as an additional optimization step after PGO.
For the Rust projects, I recommend starting with cargo-pgo.
I understand that the project is in the earliest stages of its lifecycle. So just think about the issue as a possible idea for improvements.
The text was updated successfully, but these errors were encountered: