Azure Traffic Manager - Performance Routing - Counter-performing responses times

0
votes

I have an Azure Mobile App backedn with a West Europe endpoint and a Brazil endpoint.
I use Azure Traffic Manager with the routing method set to Performance.

When I test the responses times from Brazil (via this site for example) I endup with counter performing results:

  • testing the Brazil endpoint directly: 0.3s
  • testing the West Europe endpoint directly: 2.3s
  • testing through Traffic Manager: 2.6s


I also checked (via this site) that traffic manager was indeed pointing to the Brazil endpoint ip from Brazil and to the West Europe endpoint ip from the rest of the world.

As you can imagine these were not the expected results.

UPDATE

Some screenshots.
Here are the results for the TrafficManager endpoint:

enter image description here

Here are the results for the Brazil endpoint:

enter image description here

UPDATE 2

I should mention that the exact same tests were returning good and expected results a few weeks ago when I setup Traffic Manager. I re-did these tests because users (rightfully) complained about performance.

1
azureazure-traffic-manager
Where is your database that Azure Mobile Apps is connected to? – Adrian Hall
db is in West Europe but It's not related to db. I check the root "you app is running page". And calling the brazil endpoint directly is fast. – François
testing through Traffic Manager: 2.6s do you mean that a request sent from Brazil, the response time is 2.6s? or 2.6s is average response time of all requests coming from all around the world. – Fei Han
The results shown are FROM Brazil. – François
I updated the question with screenshots showing results from different cities in the world. – François

1 Answers

0
votes

There are a couple of things that could be going on here.

  1. Traffic Manager has a problem - unlikely, but if all the other thoughts are not working, then this is likely the culprit.
  2. The Azure Web Site is cold starting. The first request to an Azure Web Site causes it to start (unless you have warmed up the site and turned "Always On" on).
  3. Something else could be going on with the VM that supports the Azure Web Site.

Try hitting the underlying site a few times. Ignore the first result. That should tell you if it's the traffic manager, the web site itself or the cold start problem.