Mittwoch, 11. April 2012 13:28
I am not sure if this is the right forum, but this is my question.
I have an Azure project, which is working fine and already in production. What we want to do is run the website on our local IIS for testing purposes. We are having a performance issue where the first page (Login) takes up to 20 seconds to appear. I have researched on the issue and some mention a compiling issue where the IIS server has to compile the webpage; however, if that is the case, it seems like IIS is compiling the webpage every time IE is closed/opened as this only happens when closing the web browser and reopening it. If we keep IE opened and open the page in a new tab, it loads instantaneously.
My question is: Does the project being an Azure project have something to do with this?
Any ideas why this could be happening?
Thanks in advance.
Mittwoch, 11. April 2012 13:44Moderator
Have you verified if there are any Azure dependencies in the web application? Could it be there's an operation in the page load that is waiting for a time-out before the page is displayed?
In my experience, there's nothing inherent in an Azure web role that would cause a delay.
Mittwoch, 11. April 2012 13:55
Thanks for your reply.
I see "Microsoft.WindowsAzure.Diagnostics", "Microsoft.WindowsAzure.ServiceRuntime", and "Microsoft.WindowsAzure.StorageClient" in the references folder. I am not sure if these are considered dependencies. Checked Page load and everything looks fine, no data loads, time-outs, etc.
Donnerstag, 12. April 2012 02:46Moderator
"Microsoft.WindowsAzure.Diagnostics", "Microsoft.WindowsAzure.ServiceRuntime", and "Microsoft.WindowsAzure.StorageClient" are necessary references of Windows Azure for general application, you can keep them.
Would you like to deploy a simple application on Windows Azure Platform to reproduce this problem? Does your application runs OK (Within 20 seconds) in local environment?
Donnerstag, 12. April 2012 18:45Moderator
If you don't need those assemblies, you can try dropping them out and see if that changes anything. But I would suspect that somewhere there's something that's trying to call out to Windows Azure and is timing out.
Try firing up a tool like Fiddler and looking for calls to Windows Azure. If you see them, this could be the culprit.
Freitag, 13. April 2012 15:31
Figured it out.
When the application starts, it establishes a connection to our SQL database to retrieve some settings. Since I was testing locally, I never had any issues connecting to my local SQL. After I placed the files in IIS, my local SQL needed to allow connections in our network. That was my issue.
Thanks for the suggestions guys.
- Als Antwort markiert admdev Freitag, 13. April 2012 15:31