NOTE: You should perform these optimizations on all servers that
OctaGate Switch will serve pages for, including the OctaGate Switch server! Use
this registry file for the web servers.
NOTE 2: If you haven't performed these actions before, you may have to
restart your server once you're done.
Optimize HTTP Switchboard
When HTTP Switchboard installs for the first time, it will suggest that you change your settings
to guarantee maximum performance while using HTTP Switchboard;
HTTP Switchboard will perform these changes for you, but if you prefer, you can use the
registry file located here to perform the changes
manually. Just right click on the downloaded file and select "Merge" (or double click on the file).
These exact same changes are recommended by Microsoft under
similar
conditions.
Why these optimizations?
The short answer is, it will radically increase the number of
hits per second HTTP Switchboard can cope with. We've yet to have an issue
raised by this, but we still strongly urge that you perform these changes.
The long answer is, when HTTP Switchboard relays pages from a
Web Server or a Web Application, it behaves in a fashion peculiar to TCP/IP : it
servers an extreme amount of pages from the same IP:Port (OctaGate Switch) to the same IP:Port (Web Server). TCP/IP has a limitation that each combination of IP:Port
must be unique, which is not a real problem when browsers connect each using a
unique IP. But since OctaGate Switch connects to the Web Server from the same IP number
each time, the server runs the risk of running out ports.
With the above suggested optimizations, the theoretical limit
of connections / second comes out at about 1100 connections per second, which is
a huge amount by any standard.
If you want to read more about the changes you're about to make to your registry, we suggest
that you read these documents:
