While synthetic workloads do a great job of testing the underlying technology and reporting easy to understand results, they aren’t always indicative of how the drive will be used by the end user. Workloads that simulate enterprise environments try to bridge that gap without being overly complex.
The database profile is 8K transfers, and 67% percent of operations are reads.
The exchange server profile breaks down on a 68% read/32% write bias, composed of only 32K transfers. It is similar in terms of read write mix to the database profile, but the primary transfer size of 32K is four times larger.
The fileserver profile is based on an 80% read/20% write mix. Its made up of blocksizes from 512 to 64K, each making up a different percentage of the access pattern.
The pattern is: 512 bytes=10%, 1k=5%,2k=5%, 4k=60%, 8k=2%, 16k=4%, 32k=4%, 64k=10%.
The webserver profile is similar to the fileserver profile, but has some additional 128K and 512K accesses thrown in for good measure. Additionally, the profile is 100% read.
In our server profile tests ,the P400m performed very predictably. It properly scaled from low queue depths, while leveling off around 16 threads. Pushing it beyond 32 threads did not yield any greater performance.