We put together a fun infographic to compare using the debugger vs. a profiler for troubleshooting slow page loads in ASP.NET apps. This coincides with our recent release of LeanSentry’s slow operation tracking, which provides an lighter (and more informative) alternative to either.
Here it is:
What do you use currently? Do you agree with our take? Leave comments.
But isn’t it like the (free) http://miniprofiler.com/ ?
Hi Ofer,
I am not an expert on miniprofiler, but here is what I know – it’s got a similar approach (adding trackers).
But, it also has some significant differences:
1. LeanSentry aggregates slow operation information and tracks it over time/multiple requests. Miniprofiler focuses on a single request.
2. Its linked with detailed request traces of the slow requests.
Overall, LS tries to provide a comprehensive history of slow operations and how they impact slow requests in your app.
Then we also rope this info into troubleshooting tasks, which lets you zero in and diagnose specific urls in a simple stepby-step wizard.
If you have any feedback on LS vs. miniprofiler, I’d love to hear it!
Best,
Mike