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
Is your feature request related to a problem? Please describe.
Not exactly a problem. Just an idea of how to possibly improve the OpenSIPS performance.
Describe the solution you'd like
Recently I checked Profile-Guided Optimization (PGO) and Post-Link Optimization (PLO) improvements on multiple projects. The results are available here. According to the tests, these optimizations can help with achieving better performance in many cases for many applications: networking apps like HAproxy and Envoy, many databases (could be useful for cached), parsing utilities like Vector, etc. Since this, I think trying to optimize OpenSIPS with PGO and PLO can be a good idea. Having faster OpenSIPS can help with serving more users per CPU core with OpenSIPS and reduce Total Cost of Ownership (TCO) for the solution.
Implementation
I can suggest the following action points:
Perform PGO benchmarks on OpenSIPS. If it shows improvements - add a note to the documentation about possible improvements in OpenSIPS performance with PGO.
Providing an easier way (e.g. a build option) to build scripts with PGO can be helpful for the end-users and maintainers since they will be able to optimize OpenSIPS according to their workloads.
Optimize pre-built OpenSIPS binaries
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.
Describe alternatives you've considered
Do not use PGO and PLO optimizations and possibly miss some performance.
Is your feature request related to a problem? Please describe.
Not exactly a problem. Just an idea of how to possibly improve the OpenSIPS performance.
Describe the solution you'd like
Recently I checked Profile-Guided Optimization (PGO) and Post-Link Optimization (PLO) improvements on multiple projects. The results are available here. According to the tests, these optimizations can help with achieving better performance in many cases for many applications: networking apps like HAproxy and Envoy, many databases (could be useful for cached), parsing utilities like Vector, etc. Since this, I think trying to optimize OpenSIPS with PGO and PLO can be a good idea. Having faster OpenSIPS can help with serving more users per CPU core with OpenSIPS and reduce Total Cost of Ownership (TCO) for the solution.
Implementation
I can suggest the following action points:
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.
Describe alternatives you've considered
Do not use PGO and PLO optimizations and possibly miss some performance.
Additional context
Here I collected several PGO-related links (more PGO-related materials available at https://github.com/zamazan4ik/awesome-pgo/).
Examples of how PGO optimization is integrated into other projects:
configure
scriptI have some examples of how PGO information looks in the documentation:
Regarding LLVM BOLT integration, I have the following examples:
I hope these ideas could be interesting for someone from the OpenSIPS community.
The text was updated successfully, but these errors were encountered: