Tools for stress-profiling Blazor Server application

[mkArtakMSFT]

We had the internal Ignitor tool which we used to stress Blazor apps and measure different characteristics of sample apps.
This issue tracks the potential for productizing that tool so customers can use it to measure the load for their apps.

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[CommonLoon102]

I wouldn't agree with the affected-few label. If Blazor Server-side wants to be more than just a PoC, or a quick solution for a school project (similarly what LINQ to SQL was), then this is a strong requirement. Serious projects won't be started on this technology if it is not possible to verify that it will fulfill the needs later. Management won't allow to start something serious and huge in a new technology if they can't make sure that when it comes to that point when it will serve thousands of users simultaneously, then it won't break. Or it won't break, but will be too slow for the use-case.

Stress-testing can also reveal hidden concurrency issues before they surface for the users.

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[TheXenocide]

Hi there! We use the Ignitor tool for stress testing internally and I can't help but notice that the project has been deleted in the main branch. Does this mean this ticket is being abandoned? How will we stress test our Blazor-server app in the future?