Limitations of number of sites in IIS

Hi,

The company i work is merging the sites that were on 2 servers to a new one.

The new server:
Double Xeon 3,4
4,0 GB RAM
windows 2000 server, SQL2000, primary DNS service

SQL2000 is limited to use 512Mb by the moment.
One component to image resizing uses a lot of memory, but cleans it in half
an hour.

The IIS have 3-4 sites running in HIGH ISOLATION MODE, due some problems
that they have and developers of them are trying to see whats the problem
with them.

Everything working fine and fast, besides the 3-4 sites i mencioned.

99% of sites are ASP's, not static.

2 Portals with tons of access by day, and one of them have problems, i think
due the progamed ASPs, it use time to time a LOT OF MEMORY and gives an error
on event viewer, but site doesnt stop to work.

Bandwith of server is 5MB located in datacenter in an ISP.

Its reaching 700 sites and need around more 150 sites to get all in the new
server, and eventually new sites every month, 5-10.

And now the question:
How can i check if the IIS can handle so many sites, or if there is any
number of limite of sites for IIS in windows 2000 server.
Just to can preview or if its recomend to use another server distributing
sites.

Tkx in advance,
PV

Phil
Wed Feb 22 10:31:25 CST 2006

PV wrote:

> Hi,
>
> The company i work is merging the sites that were on 2 servers to a new one.
<snip>
> Its reaching 700 sites and need around more 150 sites to get all in the new
> server, and eventually new sites every month, 5-10.

First, IIS has no hard coded limit. All you can do is monitor the performance
and decide when 'enough is enough'.

Second, I would NEVER run primary DNS on the web server, at least not without
virtualization. IIS is more likely to crash and force a reboot than DNS.

Third, I would use a cluster for more than a few dozen sites. Can you afford to
have 700+ sites go down for hours if the hardware fails?

--
Phil Frisbie, Jr.
Hawk Software
http://www.hawksoft.com