First of all a mainboard design must be really neat and clean - if it isn't, you might not be able to
use really fast timings on the RAM array, or you might even need to leave a couple of performance
enhancement features in the chipset disabled that affect AGP, PCI or IDE busses.
Then of course enabling all those performance enhancements and aggressive memory timings
needs thorough verification, and by far not everyone puts this huge amount of work into it -
the geek community is so keen on having the latest stuff, no matter whether it's finished or
not, that you lose quite an amount of customers if you're out "late" (which would be _after_
testing). Just look at how long it takes in the server and high end workstation market between
presentation of a chipset and actual product shipment ... this isn't "problems", its testing.
But whatever market you're in, whatt you release to customers must work with an almost infinite
number of combinations, so quite often you rather go with quite conservative settings in early BIOSes,
and maybe later cautiously tune it upward. In the server corner, there is more time to test and
tune things, so initial release performance is much closer to what the hardware might be able
to do.
Other than in setting up the hardware and assisting in booting up the operating system, BIOS
isn't much involved in running the system. Only in power management handling it gets to do
something, with little to no effect on speed when fully powered.
Finally, with all of the above being done and perfected, all boards using the same stuff should
benchmark the same. So why don't they? Some companies like to cheat a little on the clock
frequency ... e.g. ASUS boards have been caught running at up to 137 MHz when set to 133, and of
course this speeds up everything by 3 percent over a board that doesn't cheat. Kind of like car
manufacturers sending out "special" cars for reviews, with a few extra horsepowers to give theirs
the edge over a "comparable" competitor product.
regards, Peter