We have a Line of Business app serving ~450 users - mostly with the app open most of the day. We are running 3 instances of P3V3 app service during core business hours and 2 instances out of hours.
We're seeing 20M messages per day and our Azure SignalR Service costs are double the app service cost.
When we use websockets, our users complain about intermittent SignalR circuit drop outs.
We are not using SignalR for anything other than blazor.
We have raised the issue with MS but they're not really interested.
So far we have found no way to save costs on SignalR - no reservations and you have no control over the messages blazor is sending.
Our app is using Styncfusion blazor components. Have others experienced similar issues or are we doing something wrong?