Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Commit 97b535f

Browse files
authored
Finalizing layout of benchmarking.md file
1 parent 1f30ed0 commit 97b535f

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

Documentation/project-docs/benchmarking.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -66,12 +66,10 @@ public class Program
6666
}
6767
```
6868

69-
## Alternative 3 - Benchmarking with multiple or custom .NET Core 2.1 SDKs
70-
Whenever you want to benchmark an application with one or multiple different .NET Core 2.1 run time framework versions simultaneously, you want to create a manual BenchmarkDotNet configuration file.
71-
69+
# Benchmark multiple or custom .NET Core 2.x SDKs
7270
Follow the instructions described here https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/dogfooding.md#advanced-scenario---using-a-nightly-build-of-microsoftnetcoreapp and skip the last part which calls the `dotnet.exe` to run the application.
7371

74-
Add the desired amount of Jobs and add `NetCoreAppSettings` to specify the `targetFrameworkMoniker`, `runtimeFrameworkVersion` and `customDotNetCliPath` for each:
72+
Whenever you want to benchmark an application simultaneously with one or multiple different .NET Core run time framework versions, you want to create a manual BenchmarkDotNet configuration file. Add the desired amount of Jobs and `NetCoreAppSettings` to specify the `targetFrameworkMoniker`, `runtimeFrameworkVersion` and `customDotNetCliPath`:
7573

7674
```csharp
7775
public class MainConfig : ManualConfig
@@ -89,6 +87,9 @@ public class MainConfig : ManualConfig
8987

9088
// Job #2 which could be in-process (see Alternative #2)
9189
// ...
90+
91+
// Job #3 which could be .NET Core 2.0
92+
// ...
9293
9394
// Add whatever jobs you need
9495
Add(DefaultColumnProviders.Instance);
@@ -116,9 +117,9 @@ public class Program
116117
}
117118
```
118119

119-
## Running the benchmark
120+
# Running the benchmark
120121

121-
To get valid results make sure to run your project with RELEASE configuration:
122+
To get valid results make sure to run your project in RELEASE configuration:
122123

123124
```
124125
cd "path/to/your/benchmark/project"

0 commit comments

Comments
 (0)