This topic contains the following sections:<\/p>\n
- \n
- Using the StopWatch filter to time every action method<\/a> <\/li>\n
- Configure Azure settings from Visual Studio<\/a> <\/li>\n
- Configure app settings for Azure<\/a> <\/li>\n
- Limitations of the Perf filter<\/a> <\/li>\n<\/ul>\n
Using the StopWatch filter to time every action method <\/h2>\n
Add the StopWatch NuGet package to your ASP.NET MVC app using the following command in the Package Manager Console<\/a>:<\/p>\n
PM> Install-Package StopWatch<\/code><\/p>\nThe StopWatch package will create a Filter<\/em> directory and add a class containing the
UseStopwatch <\/code>attribute. You can apply this filter to controllers with the following syntax:<\/p>\n[UseStopwatch]\r\n<\/span>public class <\/span>HomeController <\/span>: <\/span>Controller\r\n<\/span>{<\/span><\/pre>\n<\/a><\/p>\n
To apply it globally (that is to every controller), add the following code to the App_StartFilterConfig.cs<\/em> file:<\/p>\n
public class <\/span>FilterConfig\r\n<\/span>{\r\n <\/span>public static void <\/span>RegisterGlobalFilters(<\/span>GlobalFilterCollection <\/span>filters)\r\n {\r\n filters.Add(<\/span>new <\/span>HandleErrorAttribute<\/span>());\r\n filters.Add(<\/span>new <\/span>UseStopwatchAttribute<\/span>());\r\n }\r\n}<\/span><\/pre>\n<\/a><\/p>\n
Add settings to the root web.config<\/em> file to control how timing information is sent to the trace system. For development we want all requests to be under 250 MS. Action methods taking more than 500 MS are recorded at the warning level, and requests taking more than 2.5 seconds are considered errors. In the markup below, we’ve also set
ShowTimeInLayout <\/code>to 1 (true), so every page will display the elapsed time. We will show timing information for each page in development and test, but not in production. Later in the tutorial I\u2019ll show how to set these values outside of source code for the Azure environment.<\/p>\n<\/<\/span>connectionStrings<\/span>>\r\n<<\/span>appSettings<\/span>>\r\n <<\/span>add <\/span>key<\/span>=<\/span>"<\/span>webpages:Version<\/span>" <\/span>value<\/span>=<\/span>"<\/span>3.0.0.0<\/span>" <\/span>\/>\r\n <!-- <\/span>Keys deleted for clarity. <\/span>-->\r\n<\/span> <<\/span>add <\/span>key<\/span>=<\/span>"<\/span>TraceErrorTime<\/span>" <\/span>value<\/span>=<\/span>"<\/span>2.5<\/span>" <\/span>\/>\r\n <<\/span>add <\/span>key<\/span>=<\/span>"<\/span>TraceWarningTime<\/span>" <\/span>value<\/span>=<\/span>"<\/span>.5<\/span>" <\/span>\/>\r\n <<\/span>add <\/span>key<\/span>=<\/span>"<\/span>TraceInformationTime<\/span>" <\/span>value<\/span>=<\/span>"<\/span>.25<\/span>" <\/span>\/>\r\n <<\/span>add <\/span>key<\/span>=<\/span>"<\/span>ShowTimeInLayout<\/span>" <\/span>value<\/span>=<\/span>"<\/span>1<\/span>" <\/span>\/>\r\n<\/<\/span>appSettings<\/span>>\r\n<<\/span>system.web<\/span>><\/span><\/pre>\n<\/a><\/p>\n
The last change we need to make is to add the timing information to the ViewsShared_Layout.cshtml<\/em> file:<\/p>\n
<<\/span>footer<\/span>>\r\n <<\/span>p<\/span>> <\/span>@<\/span>Html.Encode(ViewBag.elapsedTime) <\/span><\/<\/span>p<\/span>>\r\n<\/<\/span>footer<\/span>><\/span><\/pre>\n<\/a><\/p>\n
Run the app, each page shows the elapsed time for the action method.<\/p>\n
![\"r1\"](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2014\/07\/5367.r1_thumb-2.png\" "\\"r1\\"")
<\/a> <\/p>\nIf you’re running in Visual Studio, you can see the trace data in the output window:<\/p>\n
![\"outputWinTrace\"](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2014\/07\/6443.outputWinTrace_thumb-2.png\" "\\"outputWinTrace\\"")
<\/a> <\/p>\nConfigure Azure settings from Visual Studio<\/h2>\n
Deploy the app to Azure where you can see the page level timings. <\/p>\n
You can configure Azure settings in the Azure portal or in Visual Studio. Most of the steps in the following section will be done in Visual Studio, but they are easily done in the Azure portal. In Server Explorer<\/strong>, navigate to your web site (con2<\/strong> in the image below), right click > View Settings<\/strong>.<\/p>\n
![\"Avs\"](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2014\/07\/8424.Avs_thumb-2.png\" "\\"Avs\\"")
<\/a> <\/p>\nSet the Application Logging<\/strong> level to Verbose<\/strong>. The Verbose<\/strong> level logs all trace message. Setting it to Information<\/strong> logs Information<\/strong>, Warning<\/strong> and Error<\/strong> levels. Setting it to Warning<\/strong> logs Warning<\/strong> and Error<\/strong> levels. You can set the logging level in the Azure portal on the Configure<\/strong> tab of the web site:<\/p>\n
![\"configPortal\"](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2014\/07\/3250.configPortal_thumb-2.png\" "\\"configPortal\\"")
<\/a> <\/p>\nRun the app on Azure, and in Visual Studio, navigate to your web site, right click > View Streaming Logs:<\/strong><\/p>\n
![\"avs2\"](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2014\/07\/6470.avs2_thumb-2.png\" "\\"avs2\\"")
<\/a> <\/p>\nThe output window in shows the trace data. Note the filter lists all the route data plus any query string data.<\/p>\n
![\"AzTrace\"](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2014\/07\/7384.AzTrace_thumb-2.png\" "\\"AzTrace\\"")
<\/a> <\/p>\nLooking at trace data from Visual Studio is interesting, but it’s not a viable approach to production monitoring. A good way to save trace data on Azure is to connect the trace provider to Azure storage.<\/p>\n
![\"AcreateStorage\"](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2014\/07\/2110.AcreateStorage_thumb-2.png\" "\\"AcreateStorage\\"")
<\/a> <\/p>\nIn Server Explorer<\/strong>, right click Storage<\/strong> > Create Storage Account<\/strong>.<\/p>\n
![\"ACSA\"](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2014\/07\/8715.ACSA_thumb-2.png\" "\\"ACSA\\"")
<\/a> <\/p>\nIn the Azure portal, click on your web site and select the Configure<\/strong> tab. Under application diagnostics <\/strong>set application logging (blob storage)<\/strong> to On<\/strong>. Set the logging level to Information<\/strong>. Click the manage blob storage button and enter the storage account you created. (Note: if you don’t see the storage account you created from Visual Studio, navigate to the storage account in the portal and force a full refresh of the browser (^F5)).<\/p>\n
![\"z\"](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2014\/07\/0878.z_thumb-2.png\" "\\"z\\"")
<\/a> <\/p>\nClick Save<\/strong>. Test you web app so you can generate trace data. <\/p>\n
In Server Explorer<\/strong>, navigate to the blob storage you created and double click on the container.<\/p>\n
![\"z1\"](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2014\/07\/1070.z1_thumb-2.png\" "\\"z1\\"")
<\/a> <\/p>\nDouble click on the trace data log to open it in Excel.<\/p>\n
You can use Excel to sort the data and hide columns you’re not interested in.<\/p>\n
![\"e\"](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2014\/07\/4544.e_thumb-1.png\" "\\"e\\"")
<\/a> <\/p>\nConfigure app settings for Azure<\/h3>\n
In Server Explorer<\/strong>, navigate to your web site (con2<\/strong> in the image below), right click > View Settings<\/strong>.<\/p>\n
![\"Avs\"](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2014\/07\/6710.Avs_thumb_1-1.png\" "\\"Avs\\"")
<\/a> <\/p>\nUnder Application Settings<\/strong>, hit the Add<\/strong> button to add the app settings from the web.config<\/em> file. The app settings here will override those in the web.config<\/em> file. On a production app, we won’t want to show page timings.<\/p>\n
![\"zz\"](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2014\/07\/2437.zz_thumb-1.png\" "\\"zz\\"")
<\/a> <\/p>\nLimitations of the Perf filter<\/h3>\n
The simple stopwatch filter misses the authorization portion of the ASP.NET pipeline (which can be expensive), and it stops timing after the OnResultExecuted<\/a> completes. The filter completely ignores client side timing, which can be significant. Glimpse<\/a> is a much more powerful tool to profile and monitor your ASP.NET app – stay tuned, I’ll be blogging on that next.<\/p>\n","protected":false},"excerpt":{"rendered":"
Successful web app dev teams generally consider performance a requirement from the beginning, not an afterthought. Performance should be considered in all phases of a project, from design and into production, including updates to the app. That’s not to say you should try to optimize code before you’ve measured it, you really don’t know what […]<\/p>\n","protected":false},"author":415,"featured_media":58792,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197],"tags":[7333,37,46,7439,7295,108,7474,7475,7448,7476,7272,147,7415],"class_list":["post-364","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aspnet","tag-asp-net-mvc","tag-azure","tag-c","tag-mvc-5","tag-perf","tag-performance","tag-pipelinestage","tag-profile","tag-routing","tag-time","tag-tips-and-tricks","tag-visual-studio","tag-windows-azure"],"acf":[],"blog_post_summary":"
Successful web app dev teams generally consider performance a requirement from the beginning, not an afterthought. Performance should be considered in all phases of a project, from design and into production, including updates to the app. That’s not to say you should try to optimize code before you’ve measured it, you really don’t know what […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/364","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/415"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=364"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/364\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/58792"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=364"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=364"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=364"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Configure Azure settings from Visual Studio<\/a> <\/li>\n