If one team of people configured both machines, then one of them probably wasn't set up right. We should stop doing web benchmarks against computer hardware and start doing benchmarks against money.
Two teams should be set up representing 'experts' in either IIS or Apache. Each team is given the same amount of money to create and configure the best web machine they can with that money. The money will be charged for hardware, software, and hours of labor (for setup and configuration). Then those machines could be benchmarked (with static and dynamic content) against each other.
This would allow proper configuration of each machine and the benchmark would be against the real bottom line --Money.
Slashdot Mirror
This is probably redundant by now, but...
If one team of people configured both machines, then one of them probably wasn't set up right. We should stop doing web benchmarks against computer hardware and start doing benchmarks against money.
Two teams should be set up representing 'experts' in either IIS or Apache. Each team is given the same amount of money to create and configure the best web machine they can with that money. The money will be charged for hardware, software, and hours of labor (for setup and configuration). Then those machines could be benchmarked (with static and dynamic content) against each other.
This would allow proper configuration of each machine and the benchmark would be against the real bottom line --Money.