Add performance benchmark harness - #56
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 an isolated performance benchmark suite for EvolvePHP 2 without changing production framework behavior.
The benchmark harness covers application boot, service-container resolution, execution lifecycle, persistent-style sequential execution, routing, middleware dispatch, and full HTTP kernel execution.
It also adds environment fingerprinting, normalized benchmark results, local-result isolation, correctness checks, and benchmark-specific dependency management.
Benchmark fixture construction is kept outside measured hot paths so route matching and container resolution reflect the operations being measured rather than setup cost. First-resolution service benchmarks also use single-revolution, zero-warmup execution so they retain true first-resolution semantics.
Validation
The benchmark results produced during development are environment-specific and are not presented as cross-framework performance claims.