Geek asks and answers

Publish to Windows Azure in Debug or Release Mode

I have a Windows Azure application (Asp Net Mvc 4). And there is ajax in this application. Some queries with simple server logic in memory (no sql, no external web services). When I run it locally in debug mode, it takes about 900 ms for an ajax request to request a response. Locally in release mode, it takes about 30 ms (this is normal). When I publish an application for Azure, it takes 450ms to get a response. I try both debug mode and release, as well as cloud and on-premises configuration. In all cases, it takes 450 ms. Question: is there something that I did not take into account?

+3
source share
1 answer

To properly diagnose the performance of your ASP.NET MVC application, you need to consider:

  • The delay between your client computer and the server. Use the ping utility to measure it.
  • The time required to establish an HTTP and / or HTTPS connection.
  • The time it takes to wait for other simultaneous requests that your browser may issue.
  • Data transfer time, both for sending a request and for receiving a response.
  • Queue on web server due to congestion.
  • The time spent on the server actually processes the request. You can measure this with the StopwatchAttribute described in this article . Use the current code from GitHub though, because the code in the article is not compatible with ASP.NET MVC 3.

, Chrome Internet Explorer, Firefox Firebug Yahoo YSlow, .

+1

More articles:


All Articles