-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Introducing BenchmarkDotNet benchmarks #3475
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
Conversation
Where does the output from these get stored? |
Default location is |
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.
Looks good to me
@Horusiath got a warning back that the API specs had failed for Streams and Core. No idea why. Rebased on the latest |
Beside adding |
We'll see what it says on this run. |
7e39daf
to
0fd5ebf
Compare
@@ -1,4 +1,5 @@ | |||
[assembly: System.Runtime.CompilerServices.InternalsVisibleToAttribute("Akka.Cluster")] |
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.
Ah I see.. It was the internals stuff
This PR introduces new benchmarking project using BenchmarkDotNet. So far following cases have been included:
Akka.IO.ByteString
benchmarks including byte string creation, concatenation and slicing.Akka.Util.FastLazy
value materialization comparison with nativeSystem.Lazy
.Type.TypeQualifiedName()
compared toType.FullName
.ActorPath
andAddress
parsing, concat, comparison and equivalence benchmarks.There are also two monitored benchmarks, that shouldn't count as microbenchmarks, but BenchmarkDotNet can do them too:
Those 2 checks can potentially make PingPong.csproj and SpawnBenchmark.csproj obsolete.
I'm hoping to introduce more benchmarks in future PRs.