Performance Tests: Update the base point to compare against #51689
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.
Recently in http://codevitals.run the numbers for Gutenberg metrics started showing weird results. I suspect that this happened is because the new "base point" we picked to compare against was not a commit in "trunk" which means it didn't have any "previous data" attached to it. So it's like we started a new graph that is unrelated to previous values.
In this PR, I'm changing the base point again, I've picked a commit that:
After this PR will be merged, I'll update the database of codevitals and remove all the numbers after the change of the "base point".