Hacker News Reader

Banwidth != latency, however.

A truckload of TB disks will give you awesome bandwidth by driving it around to the destination.

The latency of a particular call, however, wouldn't make it usable.

Memory is hierarchical, but any latency beyond NVMe is non factor for treating remote data as memory

Agreed on light speed (latency). But the majority of the consuming applications need to process that data. If we have enough data to process, latency is only visible until the first initial bytes. After that it should look seamless to consuming application.

In what use cases all remote data is required in real-time?

not necessary all data, but random data access would make you (or your application) feel the latency.

It's very rare that you are able to just ingest data in a serial fashion For most scenarios, you need to jump between locations

Think an index, reading different files, etc.

Then the latency dominates

Oh yes. If you cram a lot of data in a laser beam reflecting on one of the Apollo reflectors, your average latency (the time it takes for the right part of the beam to arrive at the receiver) will be around 1 second.

If you do that with a Voyager, it will be about a day or so, IIRC.

Reply on news.ycombinator.com