Well, IIS is not much better. Any reason why they had to tweak these settings??
Used the NIC control panel to set the following for all four NICs: Coalesce Buffers = 32 (default is 8) Receive Buffers = 1023 Transmit Control Blocks = 80 (default is 16) Adaptive Transmit Threshold = on (default is on) Adaptive Technology = on (default is on) Adaptive Inter-Frame Spacing = 1 (default is 1) Map Registers = 64 (default is 64) SMTP, FTP, MSDTC, and Browser services were disabled Set registry entries: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es: \InetInfo\Parameters\ListenBackLog=200 \InetInfo\Parameters\ObjectCacheTTL=0xFFFFFFFF \InetInfo\Parameters\OpenFileInCache=0x5000 Using the IIS Manager Set Logging - "Next Log Time Period" = "When file size reaches 100 MB" Set performance to "More than 100,000" ? Removed all ISAPI filters Removed all Home directory application mappings except.asp Removed permissions for "Application Settings" Logs on the F: drive (RAID) along with the WebBench data files Server set to maximize throughput for applications when doing WebBench tests
So much for 'smart/dynamic/self learning'.
Jim
PS - What the hell is a 'More than 100,000" setting?
Yeah no doubt. The overhead of forking new Apache(s) to handle the large number of incoming connections *will always* slow down a system.
Any good Apache administrator knows this.
Also, under the IIS configuration is says "Server set to maximize throughput for applications when doing WebBench tests", but it *does not* say this under the Apache configuration?!?
Slashdot Mirror
Yup, see http://dls.jump.net. Just got 1.54mbs/384kb/s personal service and it kicks major ass.
SWB tested the circuit at 6mb/s download.
You should see the porno fly (he, he).
Jim in Austin
"it's kind of hard to completely hide Linux,"
-- Colbat Cube --
Jim
Heh, we have Sandra Bullock...
Jim
No one (unless they are fools) sets 'StartServers' equal to 10 and then blasts it with thousands of simultaneous connections.
Might as well put out a burning building with a soda straw.
They should have set 'StartServers' to 500 or 800. Jim
Well, IIS is not much better. Any reason why they had to tweak these settings??
c es: \InetInfo\Parameters\ListenBackLog=200 \InetInfo\Parameters\ObjectCacheTTL=0xFFFFFFFF \InetInfo\Parameters\OpenFileInCache=0x5000 .asp
Used the NIC control panel to set the following for all four NICs:
Coalesce Buffers = 32 (default is 8)
Receive Buffers = 1023
Transmit Control Blocks = 80 (default is 16)
Adaptive Transmit Threshold = on (default is on)
Adaptive Technology = on (default is on)
Adaptive Inter-Frame Spacing = 1 (default is 1)
Map Registers = 64 (default is 64)
SMTP, FTP, MSDTC, and Browser services were disabled
Set registry entries:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi
Using the IIS Manager
Set Logging - "Next Log Time Period" = "When file size reaches 100 MB"
Set performance to "More than 100,000" ? Removed all ISAPI filters
Removed all Home directory application mappings except
Removed permissions for "Application Settings"
Logs on the F: drive (RAID) along with the WebBench data files
Server set to maximize throughput for applications when doing WebBench tests
So much for 'smart/dynamic/self learning'.
Jim
PS - What the hell is a 'More than 100,000" setting?
Yeah no doubt. The overhead of forking new Apache(s) to handle the large number of incoming connections *will always* slow down a system.
Any good Apache administrator knows this.
Also, under the IIS configuration is says "Server set to maximize throughput for applications when doing WebBench tests", but it *does not* say this under the Apache configuration?!?
Jim
Yeah, there is really *nothing* better than a pint of Celis, good pizza and a movie.
If you live in Austin, TX the you have to check out:
http://www.drafthouse.com/
Jim