.NET 8 Update(8): Update Benchmarks not using Dynamic PGO and BinaryFormatter #1746
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
No Dynamic PGO No 2.1.165 dependency Comparison with current beta
Update to .NET 8 No Dynamic PGO
AArnott
approved these changes
Mar 14, 2024
This was referenced Dec 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
.NET 8 enabled Dynamic PGO by default. Dynamic PGO tends to hide actual performance characteristics. Dynamic PGO should be disabled in benchmarks.
.NET 8 disabled
BinaryFormatter.This PR was originally one segment of #1744 but later I found
SerializerBenchmarkproject was actually not run in .NET 8.It was run in .NET Core 3.1.
So this PR was made in order to update all Benchmark projects to .NET 8.