ASP.NET Profiling

Question

I have a slow asp.net program running. I would like to profile the production server to see what happens, but I do not want to noticeably slow down the production server.

In general, the standard practice is to profile the production box or only local dev boxes? In addition, what programs do you recommend to run?

Answer 1

I can recommend you use dynatrace Ajax edition 3 "for client-side profiling (this is a free and easy tool) and" JetBrains dotTrace "for server-side profiling. These tools do not slow down the server, as I know.

Answer 2

You can use Tracing , and it is recommended to check it on your local computer, but if you want to check something on the server, you can enable tracing for brevity in your web.config.

ASP.NET tracing allows you to view diagnostic information about a single request for an ASP.NET page. ASP.NET tracing allows you to track the execution path of a page, display diagnostic information at runtime, and debug your application. ASP.NET tracing can be integrated with system-level tracing to provide multiple levels of trace output in distributed and tiered applications.

ASP.NET Trace Overview

Tracing in ASP.NET

Answer 3

I think the answer is really "it depends"! I would start by considering whether the program runs slowly on a production server or if it runs slowly in a development environment. I would also like to consider how much I could get a development / testing environment in line with the production environment.

Once you do this, consider if there are any areas that could be obvious bottlenecks that you could fix. So, for example, is this an ASP.NET application supported by some form of database? If so, you can monitor the database performance separately and determine if this is the problem.

Then try and be very specific about what you mean by "slow performance". Is it slowly slow (compared to what?) Or just when performing certain actions. This may give you another idea of ​​where your problem lies, or at least what questions you should ask.

Answering many of these questions, I then threw out the ANTS Performance Profiler to try to figure out what was going on. This has a pretty minimal overhead when profiling the application, and you really have to really run it for a fairly short time anyway, since you hopefully by this point should have more specific questions that you want to answer, or specific the actions you want to dig into.

Answer 4

Your best bet is the prefix ( http://www.prefix.io ). It allows you to see all of your SQL queries, logs, HTTP calls, and more.

Another option is Glimpse or the Mini Profiler.