SERVER PROFILE TESTING
To perform the server profile testing, we first have to precondition the drive. After a secure erase and 128K sequential fill, each profile is run for five hours at QD 64. After that, we run each profile for one minute at increasing QD.
The database profile is just 8K transfers, but 67% of the operations are reads.
Traditionally, the email server profile would be used. Lately, weve been experimenting with a workload t0 simulate Microsofts Exchange Email server. It breaks down 62% read and 38% write. The regular email server profile is just 8K reads on a 50%/50% read and write split.
The webserver profile is a little more complex. It’s made up of 10 different accesses: 512 bytes (22%), 1K (15%), 2K (8%), 4K (23%), 8K (15%), 16K (2%), 32K (6%), 64K (7%), 128K (1%), and 512K (1%). There are no writes, only reads.
Just out of curiosity, we ran all four traditional server profiles on the P320h for five hours. Each profile is run at a QD of 64, and each profile runs on its own thread. After the performance settles down, the P320h manages 152,000 transactions per second. Each profile levels off around 38K IOPS, despite the difference in access patterns. The Micron P320h seemingly balances the load.