5 ms·

According to this, it can take 10ms (not 100s of ms) and only for a very large read (like 32MB). https://i.gzn.jp/img/2021/06/07/reading-from-external-memory/nv

• TheDudeMan 4y ago
  (Anyone who is not running their OS and temp space on NVME should not expect good performance. Such a configuration has been very cheap for several years now.)
  • zinekeller 4y ago
    > Such a configuration has been very cheap for several years now. This is a very weird comment, considering that a) it's cheaper than yesteryear but SATA SDD (or even modern magnetic HDDs) are still sold and are in active use and b) ignores phones completely, where a large number of sites would have mobile-dominated visitors and can't just switch to an NVMe-like performance even for those with large disposable incomes (because at the end of the day even with UFS phones are still slower than NVMe latency-wise).
• deleted 4y ago
  [deleted]
• Retr0id 4y ago
  This assumes it only takes a single disk read to locate and retreive an object from the cache (which is unlikely to be the case).
  • TheDudeMan 4y ago
    OK, one small read plus one huge read would top-out at about 10.1ms, according to that graph.
    • Retr0id 4y ago
      Also a big assumption (which we could verify by looking at the relevant implementations, but I'm not going to)
  • staticassertion 4y ago
    Why is that unlikely to be the case?
    • Retr0id 4y ago
      There's going to be at least one level of indirection, and at least some of those indirections are going to be on-disk.