Many customers have high I/O rates and are "I/O bound" because of mail file sizes.

For example, reducing unnecessary code page conversion is not goign to help if your system is heavily I/O bound due to an unfortunate table space configuration.

The test site remains bottlenecked on the database server I/O and bound by performance characteristics of the database server disk.