Eric D. Mudama wrote:

Er, forgot about the queue depth of only 2...

Even in that case, you'll more than likely still get better throughput
with a single 32-MB command...  If you send a pair of queued commands
down, and the 2nd one is chosen, there's no reason that the first one
won't get starved until the very end of the request, which would have
bad latency on that command.

Well strictly, you send them one after the other. So unless you
have something similar to our anticipatory scheduler or plugging
mechanism, the drive should attack the first one first, shouldn't
it?