Share via

App container located in northeurope with reduced signalR performance

Anton Jonsson 0 Reputation points
2025-02-19T09:28:32.37+00:00

I have a number of azure app containers running in the region westeurope.
We have a database and Azure SignalR service running in northeurope that's being used by the container apps.
To reduce database latency we created a new app container environment located in northeurope and created all our container apps in that environment. When we stopped the old container apps (running in westeurope) and enabled the new app containers (running in northeurope) we started getting performance issues with SignalR. Some requests were faster than the old app containers and some were slower and even timed out after 1min 40s which made the replicas in the app container restart. We couldn't see any performance issues in SignalR service and other appliactions using signalR was working as expected. When we stopped the new container apps and restarted the old container apps they didn't have any performance issues with SignalR.

Any idea why the performance was unstable when running in northeurope?

Azure SignalR Service
Azure SignalR Service

An Azure service that is used for adding real-time communications to web applications.

Azure Container Apps
Azure Container Apps

An Azure service that provides a general-purpose, serverless container platform.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Shree Hima Bindu Maganti 7,110 Reputation points Microsoft External Staff Moderator
    2025-03-07T16:55:54.79+00:00

    Hi @Anton Jonsson ,
    Thanks for reaching out to Microsoft Q&A.
    To tackle SignalR performance issues after moving app containers to a different region, make sure the SignalR service mode is set right (Persistent vs. Serverless), cut down network latency with Azure VNet integration, and look for DNS resolution delays using Azure Private Link. Also, check that the new container environment matches the old setup, including runtime, dependencies, and configurations. Running latency tests (az network watcher connectivity check) can help spot routing issues. If SignalR connections are shaky, bumping up the minimum container instances and using sticky sessions might boost reliability. For more tips, check out the Azure SignalR Performance Guide and the Troubleshooting Guide.
    If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.
    Please let us know if you need further assistance.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.