We have a web site that works pretty swiftly in a local development environment. But once deployed to Azure it slows down to a crawl (even for a single user). Some pages take 30-60 seconds to load. Even the simplest pages take between 5 and 10 seconds.
The app is rather data intensive, so the way I see it, there is a slow connection between the web node and SQL node. We currently use S2 instance, the S1 and S0 didn't work at all because of timeouts. When we execute queries directly against the database, they all return within milliseconds, so it is not a query performance issue. It seems that there is a big penalty on establishing the connection between the web node and SQL node.
I am not sure if this is a provisioning issue. At times it actually begins to work a bit faster. Not quite as fast in a local environment, but barely acceptable. But then it goes back to excruciatingly slow. Any advice is appreciated.
- Merged by Shirisha PaderuMicrosoft contingent staff, Moderator Monday, April 27, 2015 10:31 AM Same query by same person