Changes between Initial Version and Version 4 of Ticket #3787


Ignore:
Timestamp:
2022-11-23T15:19:43Z (2 years ago)
Author:
itamarst
Comment:

Once #3939 is fixed, the Pipeline class will no longer be used. However, there will still be a batching mechanism via allmydata.immutable.layout._WriteBuffer, which suffers from basically the same issue of having a single hardcoded number that isn't necessarily adapted to network conditions.

So this still should be thought about based on discussion above, but changing the summary and description.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3787

    • Property Milestone changed from HTTP Storage Protocol to HTTP Storage Protocol v2

  • Ticket #3787 – Description

    initial v4  
    1 It was added in #392, but I really don't understand the reasoning.
     1Updated issue description: there is a single hardcoded value for batching (formerly known as pipelining) immutable uploads, and it might be better to be dynamic. Or higher, at least.
     2
     3
     4----
     5
     6Initial issue description:
     7
     8Pipeline class was added in #392, but I really don't understand the reasoning.
    29
    310It makes a bit more sense if you replace the word "pipeline" with "batcher" when reading the code, but I still don't understand why round-trip-time is improved by this approach.