We've had our production service on Azure. Locally, our aspnetzero application runs pretty fast (always < 4 sec PLT) but on Azure, we are seeing extremely long load times. Some pages take over a minute to load, with typical page load times in 30 - 40 sec range. Often it seems the initial controller call seems to be taking the most time with Glimpse stating that the Action of the Controller taking the most time. It also does not appear to be a cold boot issue, since even after setting AlwaysOn = true, we see the pages become slow if now accessed after a while.
The exact same database and configuration loaded on a local or network box is many times faster. Is there something specific to Azure that inhibits Asp.NET Zero application performance? Perf profiling did not seem to show any obvious issues.
Has anyone faced these problems before? Any help on why it is working incorrectly only on Azure?
4 Answer(s)
-
0
Hi,
We didn't face such a slowness problem but we will test it again with different server/db configurations to see if there is something wrong.
By the way, can you share your SQL Server and WebSite levels/configurations for azure ? We can create the same environment on azure and test this.
Thanks.
-
0
Thanks for the reply.
<ins>The web app service details are</ins> Standard: 1 Small tier Location: West US Single instance Always On: Enabled Web Sockets: Enabled All other properties are default
<ins>The database details are:</ins> Pricing Tier: Standard: S0 Location: West US No replication or anything like that Have build index automated
I did see a small improvement when we precompiled the views and did a single DLL deployment (based on blog [http://blog.deltacode.be/2017/01/08/fix-slow-startup-of-asp-net-mvc-5-on-azure-app-services/])), but it wasn't very significant.
Other information...
I have been using the background job of ASPNetZero recently to send emails. I don't expect it to be a resource hog, and on the local machine it does not seem to have any impact.
I am getting the SocketExceptions show up in logs in Azure, but not on local machine. But since that needs an update, I've postponed doing it until I get some breathing time. [https://forum.aspnetboilerplate.com/viewtopic.php?f=5&t=5254&p=12762&hilit=audit+info+azure#p12762])
The perf drop seem to be more impacted if the site is idled for a while, maybe even 20 mins of non activity makes it feel like it has to load all over again. I did set the AlwaysOn option enabled in Azure, so can't think of what might be the reason.
Glimpse and Network Analyzer always seems to show that the system calls the Controller and then wait forever to get the data following. The css and js scripts are downloaded quickly, which makes me think it is not a network latency issue.
-
0
Hi,
Thank you very much for your detailed explanation. It might be related to Database, we will test and see it in a short time.
I will let you know the result.
Thanks.
-
0
Hi ismacagdas, any updates on this?
We are still seeing this happen and are at a loss on how to fix it.
