Post

fig (aka:[phil])
@bad-example.com

what if part of sync state was a small per-repo LRU cache of block CIDs? since most updates (at least with tid rkeys) stay on a few hot edges of the mst, maybe you could avoid sending most CIDs with most commits, just referencing a cache index instead

Nick The Sick
@nickthesick.com

Is sync not already a set reconciliation? I’m not familiar on this levels with MST and CAR, but protocol negotiation sounds like the right thing to do here

fig (aka:[phil])
@bad-example.com

every commit changes the mst root hash and that of every mst node on the path between the root and the affected key. recomputing the hashes for sync requires *adjacent* cids from unchanged nodes and records along the path. the path is usually similar from one commit to the next

0 reposts1 like