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

Published 05 May 08 11:31 by alikl
Filed under: ,

Comments

# DotNetKicks.com said on May 5, 2008 6:42 AM:

You've been kicked (a good thing) - Trackback from DotNetKicks.com

# Yossi Elkayam said on May 5, 2008 1:16 PM:

Alik :) You're A Best Practicer , Thanks

# David Groozman said on May 5, 2008 3:44 PM:

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?

# alikl said on May 5, 2008 5:50 PM:

@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

# gOODiDEA.NET said on May 6, 2008 4:49 AM:

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

New Comments to this post are disabled

Search

Go

This Blog

. My Personal Blog .

.Net Performance How To's

.Net Security How To's

Design Patterns

Impactful

Lifecycle Phases

Popular

Tools

Syndication

Page view tracker