Re: [RFC] Generation Number v2

> Jakub Narebski <jnareb@gmail.com> writes:
>> Stefan Beller <sbeller@google.com> writes:
> [...]
>>> How would this impact creation of a commit?
>>>
>>> The current generation numbers can be lazily updated or not
>>> updated at all. In my understanding of the maximum generation
>>> numbers, a new commit would make these maximum generation
>>> numbers invalid (i.e. they have to be recomputed).
> [...]
>>> For the V2 maximum generation numbers, would we need to
>>> rewrite the numbers for all commits once we recompute them?
>>> Assuming that is true, it sounds like the benchmark doesn't
>>> cover the whole costs associated with V2, which is why the
>>> exceptional performance can be explained.
>>
>> Let's check it using a simple example
>>
>> First, (minimum) parent-based generation numbers before and after
>> extending the commit graph:
>>
>>   1   2     3   4     5   6   7    new
>>   1   2     3   4     5   -   -    old
>>   .---.-----.---.-----.---*---*
>>        \
>>         \   3   4     5   6        new
>>          \  3   4     5   6        old
>>           \-.---.-----.---.
>>                  \
>>                   \   5            new
>>                    \  -            old
>>                     \-*
>
> Let me check yet another idea, using (minimum) parent-based V0 generation
> numbers (counting distance from the sink / root) as a starting number
> for source / heads commits.

> [...] but let's check another example
>
>    1   2     3   4   5   6     7   8   9       new
>    1   2     3   4   5   6     7   8   -       old
>    .---.-----.---.---.---.-----.---.---*
>         \                     /
>          \   3   4           / 5   6   7   8   new
>           \  5   6          /  -   -   -   -   old
>            \-.---.---------/---*---*---*---*