have some kind of cache for frequently accessed blocks #179

New issue

Open

opened 2021-12-25 11:46:36 +00:00 by trinity-1686a · 0 comments

trinity-1686a commented

2021-12-25 11:46:36 +00:00

Owner

For the first block of an object, it can probably reduce first byte latency by not paying the transfer time of the whole block before sending that first byte (still paying the rtt because version_table is consulted in parallel to fetching first block)

Blocks are addressed by their hash, the content can't be changed so it should be rather easy to cache (no cache invalidation required). Having gateways that can cache frequenty used blocks could reduce the load on nodes storing these blocks. For the first block of an object, it can probably reduce first byte latency by not paying the transfer time of the whole block before sending that first byte (still paying the rtt because version_table is consulted in parallel to fetching first block)