8

What kind of optimization (performance or whatever) do you use when going live with IIS (on windows 2003) ?

Currently, I use 1 application pool per web site, but I think I can do more :)

Improve this question
1
  • I tend to think about giving the images and css directory their own pool also as it just keeps active processing separate from file serving
    – Stewart Robinson
    May 1, 2009 at 12:54

4 Answers 4

Reset to default
6

Even on large banks, I've rarely (can't remember when) done any optimizations on IIS that weren't just the addition of modules. I keep all the defaults.

  • Dynamic and Static Compression
  • Set Expires dates on Static content, images, JS, etc
Improve this answer
2

Why would you consider using a single app pool per website as an optimization? Separating websites into different app pools should only be done if you have an explicit need for it like:

  • Different .NET versions
  • Different identity requirements
  • Crashing websites
  • Recycle schedules
  • Etc
Improve this answer
1
  • Crashing website : check. I have an old application (isapi module), that keeps crashing. Needs manually restarting the application pool :) I'm glad we've 1 apppool per website.
    – mathieu
    Apr 30, 2009 at 9:19
1

Lots of good articles on TechNet:

Improve this answer
1

You should see what your score is in YSlow. We run that on all sites before they deploy. A few tips:

  1. Minify your JS and combine it into one JS file (put that reference at the bottom of the html file).
  2. Combine your CSS into one file.
  3. Enable GZIP and deflate compression. Add .js and .css to the type of files it will compress. ZIPEnable is good for this.
  4. Set up content expiration for 1 year. Remember that if you modify a css/js/image file after you do this, you will need to rename that file and update references so clients pull the latest version.
  5. Disable E-Tags.
Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .