Yes? So how do you measure the performance of your .NET code?
You could instrument your code manually, but it's a laborious process annotating code, calculating times from log files, and relating it all back to your source – and then you need to remember to turn it all off later. Even worse, you often don't know what needs to be timed when you start, so most of your time is wasted finding things that aren't actually a problem…and line-level timing is hopelessly inaccurate! In a nutshell, it's clumsy, slow, and often wrong – and let's face it, you are busy enough as it is.
For a better, less time-consuming solution, try using a performance profiler. It does all the work for you and gives you accurate data. Without modifying your source, the profiler automatically collects all the CPU and wall-clock timings, and presents the results graphically, all the way down to individual lines of code. Within minutes, a profiler will show you exactly where to focus your performance-boosting work.
|
Try ANTS Performance Profiler and boost the performance of your .NET applications – fast!
- Optimize the performance of your C# and VB.NET code
- Identify performance hotspots within minutes
- Drill down to the specific lines of code causing inefficiencies
- Profile and analyze any .NET application, including ASP.NET web applications
FREE eBook: .NET Performance Testing and Optimization (Part 1)
In Part 1 of this complete guide to performance profiling, Paul Glavich and Chris Farrell explain why performance testing is a good idea, and walk you through everything you need to know to set up a test environment. This comprehensive guide to getting started is an essential handbook for any programmer looking to set up a .NET performance testing environment and get the best results out of it. Download your free copy of Part 1: Building your ASP.NET performance test environment now.
|
|
