|
2625.10.1
by Vincent Ladeuil
Add performance analysis of missing. |
1 |
Missing |
2 |
======= |
|
3 |
||
4 |
Missing is used to find out the differences between the current branch and |
|
5 |
another branch. |
|
6 |
||
7 |
The performance analysis itself brings no further points than the |
|
8 |
incremental-push-pull one. |
|
9 |
||
10 |
More importantly, the UI have been considered not optimal: missing finds and |
|
11 |
displays the differences between two branches, presenting the revisions that |
|
12 |
are not common to both branches as two sets: |
|
13 |
||
14 |
* the revisions that are present only in the current branch, |
|
15 |
* the revisions that are present only in the other branch. |
|
16 |
||
17 |
A quick and dirty survey indicates that most of the users are interested in |
|
18 |
only one set of revisions at a time. |
|
19 |
||
20 |
From a performance point of view, it may be more appropriate to calculate only |
|
21 |
the set the user is asking for. |
|
22 |
||
23 |
It has been proposed that the missing command be deprecated in favor of a |
|
24 |
--dry-run option for the push, pull, merge commands. |
|
25 |
||
26 |
In the mean time, the missing command stays interesting as it provides an easy |
|
27 |
way to test, measure and optimize graph differences processing. |