ASP.NET Performance Engineering – Stress Test Your Architecture, Design, And Code


Field experience proves – the earlier performance is tackled in development lifecycle the better results achieved. Below are most frequent practices that were most helpful in my engagement with the customers.

Architecture/Design phase

Coding phase

Unit testing phase

Performance Sins (performance anti-patterns)

My related posts

Comments (11)

  1. You’ve been kicked (a good thing) – Trackback from DotNetKicks.com

  2. Alik πŸ™‚ You’re A Best Practicer , Thanks

  3. In one hand – it is good to care about the performance all the time. But writing fast code is expensive. Fast code is more complicated and hard to maintain. Stored procedures are harder to write then code on C#. I would consider approach of writing maintainable code and optimize only when needed?

  4. alikl says:

    @Yossi

    Thanks, partner!

    @David

    Good point! Knowing what you are optimizing is key! You must decide upfront – whether to write code fast or write code that is fast πŸ˜‰

    Sometimes you cannot (impossible) to optimize code that is written without performance in mind. Sometimes you need to redesign or even to rearchitect it… want to optimize on resources (time and money)? Build your app with perf in mind upfront

  5. gOODiDEA.NET says:

    .NET A-Star Pathfinding in C# JIT Optimizations Creating portable ASP.NET applications that work on IIS

  6. Alik Levin's says:

         To achieve best performance you need to make decisions based on trade-off between

  7. Alik Levin's says:

        In my previous post -  Best ASP.NET Performance Winner For Data Binding – Hands

  8. Alik Levin's says:

    In my previous post – Best ASP.NET Performance Winner For Data Binding – Hands Up To Response.Write()

  9. Es lo que me ha estado diciendo el servidor de pruebas. Esa semana la hemos dedicado a probar toda la