bench: add v0.9 benchmark suite - #27
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the v0.9 benchmark infrastructure and the five benchmark areas required by the roadmap.
Benchmark infrastructure
CPP_REQUEST_BUILD_BENCHMARKS(default OFF)cpp_request_benchmarkstargetcpp_request_benchmark_smoketarget that runs all benchmark executables with a short minimum timeBenchmark coverage
Clientkeep-alive path compared directly with a freshClient/TCP connection per requestLoopback benchmark server
CI
Adds a dedicated Release-only benchmark smoke matrix for Ubuntu, Windows, and macOS. Normal six-job build/test CI keeps benchmarks disabled, so ordinary development builds do not pay the Google Benchmark dependency cost.
The benchmark workflow only triggers for benchmark/source/header/CMake changes relevant to the measurements.
Scope
This PR establishes benchmark executables and smoke verification. It does not make performance claims or tune implementation based on unmeasured assumptions; detailed result reporting can be done after the suite is merged and run on stable hardware.