-
Notifications
You must be signed in to change notification settings - Fork 1.1k
SAEA already in use error fix #4301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SAEA already in use error fix #4301
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
DEVHocon.Tests.Performance.ConfigFallbackLookupSpecs+Lookup_Config_Fallback_2_DeepTests how quickly Config can be looked up from the second fallback System InfoNBench=NBench, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null
OS=Microsoft Windows NT 6.2.9200.0
ProcessorCount=2
CLR=4.0.30319.42000,IsMono=False,MaxGcGeneration=2 NBench SettingsRunMode=Throughput, TestMode=Measurement
NumberOfIterations=13, MaximumRunTime=00:00:01
Concurrent=True
Tracing=True DataTotals
Per-second Totals
This PRHocon.Tests.Performance.ConfigFallbackLookupSpecs+Lookup_Config_Fallback_2_DeepTests how quickly Config can be looked up from the second fallback System InfoNBench=NBench, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null
OS=Microsoft Windows NT 6.2.9200.0
ProcessorCount=2
CLR=4.0.30319.42000,IsMono=False,MaxGcGeneration=2 NBench SettingsRunMode=Throughput, TestMode=Measurement
NumberOfIterations=13, MaximumRunTime=00:00:01
Concurrent=True
Tracing=True DataTotals
Per-second Totals
|
2x increase in lookup spec, ~40-45% drop in memory usage, 50% drop in Gen 0 GC |
DEVHocon.Tests.Performance.ConfigFallbackSpecs+Create_Config_Fallback_1_DeepTests how quickly Config can add a single fallback System InfoNBench=NBench, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null
OS=Microsoft Windows NT 6.2.9200.0
ProcessorCount=2
CLR=4.0.30319.42000,IsMono=False,MaxGcGeneration=2 NBench SettingsRunMode=Throughput, TestMode=Measurement
NumberOfIterations=13, MaximumRunTime=00:00:01
Concurrent=True
Tracing=True DataTotals
Per-second Totals
This PRHocon.Tests.Performance.ConfigFallbackSpecs+Create_Config_Fallback_1_DeepTests how quickly Config can add a single fallback System InfoNBench=NBench, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null
OS=Microsoft Windows NT 6.2.9200.0
ProcessorCount=2
CLR=4.0.30319.42000,IsMono=False,MaxGcGeneration=2 NBench SettingsRunMode=Throughput, TestMode=Measurement
NumberOfIterations=13, MaximumRunTime=00:00:01
Concurrent=True
Tracing=True DataTotals
Per-second Totals
|
Faster parse operation, but the disparity between this PR and dev gets a lot bigger the more fallbacks you add: DEVHocon.Tests.Performance.ConfigFallbackSpecs+Create_Config_Fallback_2_DeepTests how quickly Config can add a two fallbacks System InfoNBench=NBench, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null
OS=Microsoft Windows NT 6.2.9200.0
ProcessorCount=2
CLR=4.0.30319.42000,IsMono=False,MaxGcGeneration=2 NBench SettingsRunMode=Throughput, TestMode=Measurement
NumberOfIterations=13, MaximumRunTime=00:00:01
Concurrent=True
Tracing=True DataTotals
Per-second Totals
This PRHocon.Tests.Performance.ConfigFallbackSpecs+Create_Config_Fallback_2_DeepTests how quickly Config can add a two fallbacks System InfoNBench=NBench, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null
OS=Microsoft Windows NT 6.2.9200.0
ProcessorCount=2
CLR=4.0.30319.42000,IsMono=False,MaxGcGeneration=2 NBench SettingsRunMode=Throughput, TestMode=Measurement
NumberOfIterations=13, MaximumRunTime=00:00:01
Concurrent=True
Tracing=True DataTotals
Per-second Totals
|
And then the biggest winner, a 10-layer-deep DEVHocon.Tests.Performance.ConfigLookupSpec+Config_Lookup_String_10_Deep_throughputTests how quickly Config can perform a 10 deep path lookup using a string path System InfoNBench=NBench, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null
OS=Microsoft Windows NT 6.2.9200.0
ProcessorCount=2
CLR=4.0.30319.42000,IsMono=False,MaxGcGeneration=2 NBench SettingsRunMode=Throughput, TestMode=Measurement
NumberOfIterations=13, MaximumRunTime=00:00:01
Concurrent=True
Tracing=True DataTotals
Per-second Totals
This PRHocon.Tests.Performance.ConfigLookupSpec+Config_Lookup_String_10_Deep_throughputTests how quickly Config can perform a 10 deep path lookup using a string path System InfoNBench=NBench, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null
OS=Microsoft Windows NT 6.2.9200.0
ProcessorCount=2
CLR=4.0.30319.42000,IsMono=False,MaxGcGeneration=2 NBench SettingsRunMode=Throughput, TestMode=Measurement
NumberOfIterations=13, MaximumRunTime=00:00:01
Concurrent=True
Tracing=True DataTotals
Per-second Totals
|
That's a about a 3.25x increase in thoughput and we get down to zero allocations when we use a Performance numbers look good - need to look at compatibility performance inside Akka.NET integration tests. |
Wrong PR - damnit lol |
Close #4264
Issue was that after socket operation was completed, we started sending pending packages without setting "Sending" status. So it was only a matter of time when there will be some sender that will send his package at the same time last "pending" package was sent, and we got this error.
Setting "Sending" status in both cases, and all is running smooth.