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 mixed workload in our database profile caused the SM843 some issues at lower queue depths. Once we reached a queue depth of 32, the S3500 and SM843 were almost identical
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%.
We got an almost identical results with our fileserver workload. The S3500 dominated the SM843, and kept close to the S3700 until the queue depth reached 32.
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.
While the S3500 actually scored better than the S3700, it still wasn’t enough to match the SM843. Considering the workload, this should come as no surprise. Without writes to get in its way, the SM843 won going away.