By now, most of you have heard that Exchange 2007 will only be supported on x64 Hardware. That decision hinged on the impressive performance gains to be had from 64-bit's expanded access to mor...
Published Sep 08, 2006
Version 1.0
Blog Post
Chris,
Well written article! straight to the relevant stuff...
Additonal memory made available by x64 defintely helps reduce reads.
Interesting to note the checkpoint depth limit per storage group is still 20MB. In contrast with SQL server, where the checkpoint limit is specified as time (recovery interval parameter). Default interval is approx 1 min (i.e) SQL checkpoints its dirty pages every min or so. Thus the amount of flushed pages depends on the available memory size (i.e buffer cache size) and the write % in the load.
It will be interesting to know the read/write split of your load. I assume the write % of the load to be less to effect the .54 to .43 IOPS improvement.
Well written article! straight to the relevant stuff...
Additonal memory made available by x64 defintely helps reduce reads.
Interesting to note the checkpoint depth limit per storage group is still 20MB. In contrast with SQL server, where the checkpoint limit is specified as time (recovery interval parameter). Default interval is approx 1 min (i.e) SQL checkpoints its dirty pages every min or so. Thus the amount of flushed pages depends on the available memory size (i.e buffer cache size) and the write % in the load.
It will be interesting to know the read/write split of your load. I assume the write % of the load to be less to effect the .54 to .43 IOPS improvement.