Gardening (on the Web Server)

re: Gardening (on the Web Server)

jamesbl — Thu, 19 Jul 2007 21:02:33 GMT

Another reason for web gardens (honestly the only one I can truly stand behind, in addition to the above) is to break the 2GB x86 process barrier. I worked with a customer that was reaching the 2GB mark every week or so, thus making the worker process to crash. The app was not using session state, so we enabled web gardens and used 3 "flowers" (get it? flowers, gardens...my own coined term, btw. quite nerdy I admit), which spread the load over 3 worker processes and prevented them from hitting the upper 2GB limit and crashing.

re: Gardening (on the Web Server)

Tom McDonald — Thu, 26 Jun 2008 13:13:37 GMT

I like splitting the application up idea better than web gardens, but there are development environment drawbacks to that solution.

We split our main web site a while back and it help overall improve site performance. We split the app along data and presentation lines with the data part being xml over http and asp.net xml webservices (soap).

This improved the performance of the production site, but made development a nightmare. On the developers' laptops (XP running VS 2005) it was extremely difficult to mirror production.

IIS on XP can only run one site at a time. Developers can get around this by using Cassini and different ports, but Cassini wasn't viable because some of the pages (on both the data and presentation sides of the split) were classic asp pages and Cassini doesn't serve classic asp.

Bottom line: we were were able to split the app up but only along the lines of classic asp vs. asp.net.

Installation / Configuration & Recommandation pour IIS 6

Blog de l'équipe support IIS France — Wed, 10 Dec 2008 17:10:07 GMT

Voici un article présentant comment installer IIS 6 et comment le configurer, ainsi que quelques recommandations