On 6 May 2015 at 22:28, David du Colombier <0intro@gmail.com> wrote:
Since the problem only happen when Fossil or vacfs are running
on the same machine as Venti, I suppose this is somewhat related
to how TCP behaves with the loopback.
Interesting. That would explain the clock-like delays.
Possibly it's nearly zero RTT in initial exchanges and then when venti has to do some work,
things time out. You'd think it would only lead to needless retransmissions not increased latency
but perhaps some calculation doesn't work properly with tiny values, causing one side to back off