Draft
Conversation
9dd747b to
11643c0
Compare
11643c0 to
cd91387
Compare
cd91387 to
d0f0b2b
Compare
d0f0b2b to
4d600dd
Compare
4d600dd to
3b81976
Compare
3b81976 to
d30159e
Compare
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.
The original Xdebug had a performance measuring mechanism that used the count of executed instructions instead of time. This is much more precise and does not depend on random conditions which can skew timings. This PR recovers this mechanism, runs a benchmark. This benchmark is then compared with two branches: the base branch for any pull request and a "base" branch which represents the original Xdebug
In order to run this performance checks we need to add the
performance-checklabel to any PRFor now this is a draft as I need to confirm that this is running correctly and produces the right results