Not long ago in Akka.NET-land we had an issue occur where users noticed a dramatic drop in throughput in Akka.Remote’s message processing pipeline - and to make matters worse, this occurred in a production release of AKka.NET! Yikes, how did that happen? The answer is that although you can use unit tests and code reviews to detect functional problems with code changes and pull requests, using those same mechanisms to detect performance problems with code is utterly ineffective. Even skilled developers who have detailed knowledge about the internals of the .NET framework and CLR are unable to correctly predict how changes to code will impact its performance. Hence why we developed NBench - a .NET performance-testing, stress-testing, and benchmarking framework for .NET applications that works and feels a lot like a unit test.

1. .NET Performance Testing with NBench
By Aaron Stannard,
CEO, Petabridge
Founder, NBench

2. Performance is a Feature

3. A Performance Story

4. Akka.Remote Performance over
Time
0.00
5,000.00
10,000.00
15,000.00
20,000.00
25,000.00
Akka.Remote Message Throughput
MAX Messages / Second AVG Messages / Second MIN Messages / Second StdDev

5. Defensive Programming

6. Performance Lifeycle
Management

7. Where NBench Belongs

8. Performance Testing is Hard

9. NBench Isn't

10. NBench Features

11. Demo

12. .NET Performance Best
Practices

13. Get Started
https://github.com/petabridge/nbench

14. Petabridge
https://petabridge.com/