Udostępnij za pośrednictwem


Performance Code Review Tool – Practices Checker

Care about performance? Do you write your code with performance in mind? Want little help to spot performance bottlenecks automatically?

Practices Checker to the rescue.

The goal of the tool is

“Help you perform a manual code inspection by analyzing your application for potential coding and configuration settings that do not adhere to the patterns & practices ASP.NET Performance Checklist.”

The tool is available as free download here. Download, install, point to your web application solution folder and hit “Analyze” button. You will get the report for potential performance issues and recommendations on how to fix. I am sure you will be surprised by few findings.

Performance rules:

Case Study

I used Practices Checker with one of my recent engagements . The tool spotted in no time web pages where there were 30 loops, enormous amount of serialization issues, and few more.

My related posts

Comments

  • Anonymous
    February 02, 2008
    Want to spot coding anti-patterns from performance perspective without actually looking in the code?
  • Anonymous
    March 11, 2008
    How to anticipate or better off avoid performance related "surprises" during load and stress
  • Anonymous
    March 11, 2008
    How to anticipate or better off avoid performance related "surprises" during load and stress
  • Anonymous
    April 20, 2008
    These free performance tools will save you time and money identifying performance bottlenecks. Your customers
  • Anonymous
    May 04, 2008
    Field experience proves - the earlier performance is tackled in development lifecycle the better results
  • Anonymous
    July 31, 2008
         To achieve best performance you need to make decisions based on trade-off between
  • Anonymous
    July 31, 2008
        In my previous post -  Best ASP.NET Performance Winner For Data Binding - Hands
  • Anonymous
    July 31, 2008
    In my previous post - Best ASP.NET Performance Winner For Data Binding - Hands Up To Response.Write()