- User Since
- Dec 6 2017, 9:25 AM (5 w, 6 d)
Merging into the parent review.
Sun, Jan 14
I wish we could find a way to send multiple, inline, pre-generated bundles in one response. However, the existing design of compression within the bundle2 format doesn't easily facilitate this. We should think long and hard about whether to implement this feature as partial pull or extend bundle2 to allow us to do nice things and avoid the extra client-server roundtrips.
For my test case, which is a bundle of all changes in the NetBSD repo before 2014 and a yearly bundle afterwards until 2018/1/1 and normal pull for the rest, find_pullbundle needs less than 0.5s of CPU time in this iteration when it matches.
After the initial clone and with additional available changes, pull time is:
Sat, Jan 13
With the last update, the obs issues are resolved.
Which status code shall we use then, just plain 400?
Fri, Jan 12
This is a proof-of-concept. There is an interaction with obsoletion that I am still trying to understand (and fix).
Dec 11 2017
The bitset version has shown already that optimizing this is worthwhile and can eliminate up to 10% of the total size of the transaction object.
Dec 10 2017
This version should be committable. It introduces the necessary API for isolating further changes and gives a small improvement already. I'll be looking at provider a memory and time efficient sparce vector next, that's where the real benefits will be.
Dec 9 2017
Like I said, this is primarily a proof of concept. I'm still playing with different approaches and I don't think intbitset is a good fit for other reasons, but it worked the best from the various pre-existing implementations.
Dec 8 2017
This is a Proof-of-Concept and with a follow-up in D1622 to use a C implementation for the bitset.