This repository has been archived by the owner on Nov 30, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 127
Need to decrease allocations inside Helios reactors #75
Comments
Throughput is reasonable, but not great, at 100k messages per second. But the number that concerns me is memory allocation, sitting at 2,624,928.00 bytes per 1000 messages. That includes both sending and receiving of the message.... But the other part that's a bit scary is that there's no observable garbage collection at all, whcih leads me to believe there might be a memory leak. It's possible that this is just the result of Helios expanding its receive buffer, but I doubt it. Either way, about damn time we had NBench coverage for this project. |
UDP results are similar Helios.Tests.Performance.Socket.UdpThroughputSpec+OneWayThroughputBenchmarkTests a full request/response sequence for 1000 messages System InfoNBench=NBench, Version=0.2.1.0, Culture=neutral, PublicKeyToken=null
OS=Microsoft Windows NT 6.2.9200.0
ProcessorCount=4
CLR=4.0.30319.42000,IsMono=False,MaxGcGeneration=2
WorkerThreads=32767, IOThreads=4 NBench SettingsRunMode=Iterations, TestMode=Measurement
NumberOfIterations=13, MaximumRunTime=00:00:01 DataTotals
Per-second Totals
Raw DataTotalBytesAllocated
TotalCollections [Gen0]
TotalCollections [Gen1]
TotalCollections [Gen2]
[Counter] MessagesReceived
|
Done, fixed as part of 2.1 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Some specs fresh off the build server for the
dev
branch:Helios.Tests.Performance.Socket.TcpThroughputSpec+OneWayThroughputBenchmark
Tests a full request/response sequence for 1000 messages
4/13/2016 1:06:35 AM
System Info
NBench Settings
Data
Totals
Per-second Totals
Raw Data
TotalBytesAllocated
TotalCollections [Gen0]
TotalCollections [Gen1]
TotalCollections [Gen2]
[Counter] MessagesReceived
The text was updated successfully, but these errors were encountered: