Ugarit
Ticket Change Details
Login
Overview

Artifact ID: 1a2db039750e67861f597cea0a3c50a301f95eb4
Ticket: bb6d227d92cbfb3931d17cb49e0763a05030082d
Pipelined put!
User & Date: alaric 2020-05-28 14:33:57
Changes

  1. icomment:
    If we use bokbok as a backend access protocol, we can have multiple put! requests inflight. In which case, the techniques in this ticket can be applied to snapshotting as well:
    
    https://www.kitten-technologies.co.uk/project/ugarit/tktview/97b608385736f7f946bc3b3b2a037b0b8945306e
    
    OR we could continue with the original plan, kind of, and make put! fire off a thread (subject to a concurrency limit) to do the actual put, and put any errors returned into an error queue to be returned from the next operation on that storage that returns.
    
  2. login: "alaric"
  3. mimetype: "text/x-fossil-wiki"