-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Closed
Labels
C-featureCategory: Feature request or enhancementCategory: Feature request or enhancementP-mediumPriority: MediumPriority: Medium
Description
Feature Description
Not a feature - just an idea of how to improve Hyperswitch performance (CPU usage part).
Possible Implementation
Recently I did many Profile-Guided Optimization (PGO) benchmarks on multiple projects (including many 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 Hyperswitch.
I can suggest the following things to do:
- Evaluate PGO's applicability to Hyperswitch.
- If PGO helps to achieve better performance - add a note to Hyperswitch's documentation about that. In this case, users and maintainers will be aware of another optimization opportunity for Hyperswitch.
- 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:
- Rustc: a CI script for the multi-stage build
- GCC:
- Clang: Docs
- Python:
- Go: Bash script
- V8: Bazel flag
- ChakraCore: Scripts
- Chromium: Script
- Firefox: Docs
- Thunderbird has PGO support too
- PHP - Makefile command and old Centminmod scripts
- MySQL: CMake script
- YugabyteDB: GitHub commit
- FoundationDB: Script
- Zstd: Makefile
- Foot: Scripts
- Windows Terminal: GitHub PR
- Pydantic-core: GitHub PR
After PGO, I can suggest evaluating LLVM BOLT as an additional optimization step after PGO.
For the Rust projects, I recommend starting with cargo-pgo.
Have you spent some time checking if this feature request has been raised before?
- I checked and didn't find a similar issue
Have you read the Contributing Guidelines?
- I have read the Contributing Guidelines
Are you willing to submit a PR?
No, I don't have time to work on this right now
Metadata
Metadata
Assignees
Labels
C-featureCategory: Feature request or enhancementCategory: Feature request or enhancementP-mediumPriority: MediumPriority: Medium