From dd2cc577f0655f22d51b7c597fc724b64b2fa522 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?G=C3=BCnther=20Foidl?= Date: Tue, 4 Jun 2019 20:15:52 +0200 Subject: [PATCH] Added note for .NET Core 3.0 preview6+ in allocated memory --- docs/benchmarkdotnet.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/benchmarkdotnet.md b/docs/benchmarkdotnet.md index f5da8027107..871d5c20915 100644 --- a/docs/benchmarkdotnet.md +++ b/docs/benchmarkdotnet.md @@ -230,7 +230,7 @@ The results include managed memory statistics from [Memory Diagnoser](http://ada | 0.0087 | - | - | 64 B | - Allocated contains the size of the allocated **managed** memory. **Stackalloc/native heap allocations are not -included.** It's per single invocation, **inclusive**. -- **For .NET Core the Allocated Memory is only for the current thread**, see [#723](https://github.com/dotnet/BenchmarkDotNet/issues/723) for more. +- **For .NET Core 3.0 preview6+ the Allocated Memory is for all threads that were live during the benchmark execution. Before .NET Core 3.0 preview6+ the Allocated Memory is only for the current thread**. - The `Gen X/1k Op` column contains the number of `Gen X` collections per ***1 000*** Operations. If the value is- equal 1, then it means that GC collects memory once per one thousand of benchmark invocations in generation -`X`. BenchmarkDotNet is using some heuristic when running benchmarks, so the number of invocations can be -different for different runs. Scaling makes the results comparable. - `-` in the Gen column means that no garbage collection was performed.