Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
SignalR: Benchmark server logging #9264
Gives a better idea of what the benchmark server is doing. Helpful for getting an overview when using multiple crankier clients to load test.
Example from a B2s instance;
I also have this if you wanna raise multiple crankier clients in containers. Remember to pull them down when you're finished as they'll live (bill) forever if you don't turn them off.
requested review from
Apr 10, 2019
Yeah, it's not super clear but the BenchmarkServer app is actually used other benchmarking logic we do elsewhere. Introducing some locks and logging may adversely affect that benchmark.
Rather than an entirely separate app, a separate Hub with it's own endpoint URL would be OK with me.
@BrennanConroy @anurse What if instead of creating yet another benchmark server app, we added an opt-in flag like
Without the flag, we could register a
I'm still not a fan of making a precedent that we can modify the
In your other PR you were saying you are not able to build this app because of the Directory.Build.Props file which we are planning on keeping, so I'm not sure how this will help.
For load testing purposes the scenario would then be