Closed Aaronontheweb closed 3 months ago
The BIG improvements will come from making ByteString less bad inside Akka.NET, as there is a TON of memory copying that is unecessary right now.
ByteString
For significant changes, please ensure that the following have been completed (delete if not relevant):
dev
BenchmarkDotNet v0.13.12, Windows 11 (10.0.22631.3296/23H2/2023Update/SunValley3) 12th Gen Intel Core i7-1260P, 1 CPU, 16 logical and 12 physical cores .NET SDK 8.0.101 [Host] : .NET 6.0.26 (6.0.2623.60508), X64 RyuJIT AVX2 Job-WOEZAU : .NET 6.0.26 (6.0.2623.60508), X64 RyuJIT AVX2 InvocationCount=1 IterationCount=10 RunStrategy=ColdStart UnrollFactor=1 WarmupCount=0
BenchmarkDotNet v0.13.12, Windows 11 (10.0.22631.3296/23H2/2023Update/SunValley3) 12th Gen Intel Core i7-1260P, 1 CPU, 16 logical and 12 physical cores .NET SDK 8.0.101 [Host] : .NET 6.0.26 (6.0.2623.60508), X64 RyuJIT AVX2 Job-NDZWOM : .NET 6.0.26 (6.0.2623.60508), X64 RyuJIT AVX2 InvocationCount=1 IterationCount=10 RunStrategy=ColdStart UnrollFactor=1 WarmupCount=0
Ignore the mean perf number - I was focused solely on memory allocs here and was doing a ton of other work in the background. Those numbers are not reliable.
Changes
The BIG improvements will come from making
ByteString
less bad inside Akka.NET, as there is a TON of memory copying that is unecessary right now.Checklist
For significant changes, please ensure that the following have been completed (delete if not relevant):
Latest
dev
BenchmarksThis PR's Benchmarks
Ignore the mean perf number - I was focused solely on memory allocs here and was doing a ton of other work in the background. Those numbers are not reliable.