I don't think using read striping will result in optimal behaviour, because
both a slow hard drive and a fast SSD would be in the same priority category ("Standard drive"), and therefore DrivePool would apply read striping across the two drives
the slow drive could be the one with "the least outstanding requests" yet it could still be slower to use the drive for a new incoming request.
Would you consider adding a feature that allows the user to control that mirrored files should always be read from the highest-priority drive, with priority being specified by the user?
This would be a great addition for mirroring pools that use mixed drive types.
opcode got a reaction from Shane in Is it possible to control read priority?