|
|
|
|
IIS configuration
Although IIS will run once it's enabled, there are
features you'll want to turn on to keep things running smoothly
and reduce load problems.
Stopping runaway scripts - CPU
throttling
If you have the option, make sure you enable CPU
throttling. This will prevent any script from turning your
server into a slug hogging al the CPU and memory. If you
do not have this as an option in IIS then make sure you
utilize Timeout.pm. If you are
running Windows 2000 then you should use Timeout.pm regardless.
Lowering Bandwidth
Most of the stuff you're probably serving is HTML
page content. This in essence is raw text, which can be
compressed to usually less than 25% of the original size.
Of course as this is a Microsoft system if you want to add
compression it's going to cost you. IIS 6 does come with
a compression option, but from what I've read on the net
it has a few bugs. There are lots of 3rd party solutions,
the cheapest we found was httpZip
at $349.95 next was TurboIIS
for €549 and on the other end of the scale you've got
PipeBurst
at $1,499. If you want to speed up your page load times
or reduce your bandwidth costs one of these solutions is
a must.
Setting sensible homepage defaults
By default IIS only has default.htm and default.asp as
the default for a folders homepage. This list should be
much longer. This can be easily done by following
these instructions:-
- Open the 'Internet Services Manager' (program opens
with the title 'Internet Information Services'.
- Right click on your server name and select properties.
- Under 'Master Properties' select 'WWW service' and click
Edit.
- Select the tab 'Documents', you'll see the current list
of default pages.
- Click the button 'Add'.
- Use the dialog to add the following filenames:-
index.htm
index.html
index.shtml
default.html
default.shtml
index.php
index.asp
index.jsp
- Click the button 'Ok'.
- When a window pops up titled 'Inheritance Overrides'
make sure you click the buttons 'Select All' Then 'OK'.
Failure to do this will mean that you'll need to add this
setting to each website individually.
Running scripts safely and properly
Unfortunately IIS does not support CGI wrappers, so you
best option at this time is to use Timeout.pm
until our SafeRun.pm project is complete.
|
|
|
|
|
|
|
|
|
|
Want
the latest news?
Then why not sign
up for our newsletter? Be notified immediately about new
products, upgrades, sales, discounts, bug fixes, site updates
and more. |
|
|
|
|
|