chore: Add custom benchmark configs#61
Merged
neuecc merged 2 commits intoCysharp:mainfrom Mar 24, 2025
Merged
Conversation
beb5541 to
7c3bd97
Compare
7c3bd97 to
5d932ef
Compare
Member
|
Thank you! |
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.
This PR intended to add functionality to switch BenchmarkConfig via command line arguments.
How to switch benchmark config
By default.
DefaultBenchmarkConfigis used.It's almost same as existing
[ShortRunJob]+[MemoryDiagnoser]based benchmarks.And when following config key is specified as extra argument (e.g.
-- Test)Benchmark is executed with corresponding BenchmarkConfig.
List of custom BenchmarkConfig keys
DefaultInProcessTest(orInProcessMonitoring)ColdStartTargetFrameworksNuGetVersionsWhat's changed in this PR
README.mdfile.2.1. DefaultBenchmarkConfig
2.2. InProcessBenchmarkConfig
2.3. InProcessMonitoringBenchmarkConfig
2.4. ColdStartBenchmarkConfig
2.5. TargetFrameworksBenchmarkConfig
2.6. NuGetVersionsBenchmarkConfig
3.1. Add settings for
NuGetVersionsBenchmarkConfig3.2. Add cleanup target to delete BenchmarkDotNet artifacts.
2.3. Add
Cysharp/Kokubanpackage to write colored console output.Program.csto execute benchmark with custom BenchmarkConfig.[ShortRunJob]and[MemoryDiagnoser]from existing benchmarksbenchmark.yml