Monitoring and Tuning Your Server
Monitoring and Tuning Your Server |
|
In IIS 4.0, TCP sockets were allocated on a per-Web-site basis. This meant that if you created thousands of sites on one server, performance suffered. By contrast, in IIS 5.0 sockets are allocated on a per-port basis. Regardless of how many Web sites you place on any particular port, they share the sockets allocated to that port. Of course, if you put a huge number of sites on one port, performance can still suffer; if you have a mission-critical site, you can disable socket pooling for that site to avoid the risk. The relevant property is a metabase entry (MD_DISABLE_SOCKET_POOLING), which you can set at /LM/W3SVC/X (where X is the number of the site) to revert back to the IIS 4.0 default behavior.
If you choose to disable socket pooling, you should do so only at the site level, so that other (noncritical) sites can continue to take advantage of this feature. This property is not available in the IIS snap-in; you can only set it by scripting. For information about setting metabase properties, see the “Active Server Pages Guide” topic of the IIS 5.0 online product documentation.
If you have a real need to disable socket pooling globally, type the following at the command prompt:
c:\inetpub\adminscripts\cscript adsutil.vbs set w3svc\disablesocketpooling true
The command prompt will reply:
disablesocketpooling : (BOOLEAN) True
Note If pooling is enabled and you set bandwidth throttling for a site in the pool, the setting affects all the other sites as well. For this reason, it’s a good idea to disable pooling for any throttled site(s).
As an alternative to using the command line, you can change metabase settings with Metabase Editor, a tool that is distributed on the Resource Kit companion CD.