For me read speed doesn't matter that much. Continuous transfer speeds not at all. Your link doesn't fit my case.
My case is a not heavily used imap storage and I think speed drawbacks are caused by waiting for flushing the data to disk. (i.e. sending a mail: store to "Drafts", fflush, store to "Queue", fflush, store to "Sent", fflush... ). Reading should be done by OS cache here!?
But... I think I have to investigate further into it, because it seems the SD-Card has only a high delay (>300ms) with the first write. Subsequent writes are faster (~40ms). Maybe some power savings mechanism.
Still the best would be to have "write-mostly" set with the HDD (to read from SD) and "write-behind" with the SD-Card (to only wait for flushing to the HDD), because it's not throughput which annoys, but the initial delay. A combination which is impossible, since it's not possible to use "write-behind" and "write-mostly" independently.
So maybe the best is to apply write-mostly and write-behind (both) to the SD-Card. So speed depends on the HDD only, which would be fine.
|