You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the two desktop setups, the benchmarks are run on a restarted system with 5 minutes idle time before starting the benchmark. They are run with admin privileges and all unnecessary other processes are killed before running the benchmarks. For Ubuntu VPS, the benchmarks are run through continuous integration on a typical indie server setup with other processes running as well. After the benchmarks are run, a list of all running processes to make them more reproducible. To reproduce the benchmarks, run `sudo sh linux-benchmark.sh` or `win-benchmark.bat` . If you want to execute directly from the compiled program, run `./NetworkBenchmarkDotNet -b Essential`.
@@ -107,7 +119,7 @@ This is a comparison between all tests with their message throughput (higher is
107
119
108
120
## Installation
109
121
110
-
Make sure you have [.Net 5 SDK](https://dotnet.microsoft.com/download) installed.
122
+
Make sure you have [.Net 6 SDK](https://dotnet.microsoft.com/download) installed.
111
123
112
124
Then just open the solution file with Visual Studio/Rider/Visual Studio Code and build it. Note that results of the benchmarks can be very different with a different operating system and hardware.
113
125
@@ -187,7 +199,7 @@ Your favorite library is missing, or you feel like the benchmarks are not testin
0 commit comments