4 ms·
If you're writing on SATA SSD, yes. If you're writing on NVMe, well, there is a good chance that if you're not at the high end (big site, a lot of things to do
by xani_ 4y ago
If you're writing on SATA SSD, yes.
If you're writing on NVMe, well, there is a good chance that if you're not at the high end (big site, a lot of things to do), you can just ignore that as the IOPS will be "good enough"
Like, single relatively shitty NVMe can still sustain ~700MB/s of random(4k block) writes. Use good ones, and use more than one and you quickly hit CPU barrier before you hit NVMe performance.
You still want to keep it kinda grouped together but that's mostly for the wear levelling reasons
- formercoder 4y agoDoesn’t the chip on the drive deal with wear leveling?
- xani_ 4y agoIt does but it's always easier if you allocate/deallocate big blocks. Especially if you just put sub-block-size data on disk
- stingraycharles 4y agoA lot of the cloud is based on iSCSI, which, although “random access” time is relatively constant, still has an increased latency compared to local storage. As such, you definitely do want to benefit from things such as read-ahead, and designing your storage structures around these types of mechanisms yields significantly better results.