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.

[ghost]

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.

[ghost]

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?

[CommonLoon102]

@TheXenocide Hi! Can you point me to that Ignitor tool? Is it publicly available for everyone?

[TheXenocide]

@CommonLoon102 it wasn't officially supported and is no longer in the main branch, but you can still find it in the 6.x tags:

https://github.com/dotnet/aspnetcore/tree/v6.0.4/src/Components/Ignitor

Unfortunately, without it I'm not aware of any efficiently scalable option for generating significant load on the Blazor server circuits without using thousands of actual browsers (not feasible in our environment). It is limited without an actual script engine, but you can connect/maintain open connections on/navigate through pages which can be used in conjunction with a much smaller number of actual browsers reasonably well. Performing actions within a page (text changes, button clicks, etc.) starts to become a much more challenging proposition very quickly, but it suits our needs well enough (and as I mentioned, there really aren't any good alternatives I'm aware of)

[TheXenocide]

I was following up on this after my question was picked up in .NET Conf and I see here that some tags have been applied recently, which is promising. One possible suggestion presented during the presentation was to use playwright but given the number of concurrent connections we need to simulate load we've found it to be somewhat cost prohibitive, though it has been useful in conjunction with Ignitor to validate responsiveness and other more complete UX scenarios not suitable for Ignitor.

[ghost]

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.

[siata13]

Any update or recommendation about how to execute stress tests for Blazor Server project?

[garrettlondon1]

Is anything being done to help developers stress test the interactivity passing through InteractiveServer websockets rather than just http?

[TheXenocide]

Hey there, just checking in on this again because it came up in a meeting this morning. As I understand it, our performance team had some challenges setting up the old Ignitor codebase against our current .NET 8 version of the app and we will continue to need some functionality for generating load affordably going forward into new versions.