| 1 |
On Wed, Oct 27, 2010 at 09:43:50AM +0200, Dirkjan Ochtman wrote: |
| 2 |
> On Wed, Oct 27, 2010 at 09:34, Robin H. Johnson <robbat2@g.o> wrote: |
| 3 |
> > For comparison, what would the overhead costs of hg be above? |
| 4 |
> Mercurial would be about O(f + d + 10r). |
| 5 |
Thanks. |
| 6 |
|
| 7 |
> But wouldn't the real git inode space be O(35r) directly after |
| 8 |
> repacking, but grow O(rev) until the next repack? |
| 9 |
Correct, I explicitly noted "bare minimum number of inodes" for that |
| 10 |
reason. |
| 11 |
|
| 12 |
Git's more common case is: |
| 13 |
O(35r + 2c) |
| 14 |
where 'c' is the number of unpacked objects. The default repack kicks in |
| 15 |
around 6700 unpacked objects (where an object is a commit, tree, or file |
| 16 |
blob, and every commit has at least 3 objects). So it would be an extra |
| 17 |
27MiB worth of inodes until the repack kicks in. |
| 18 |
|
| 19 |
I'm also leaving out the fact that there might be a couple of pack |
| 20 |
files. In these cases, the base notation I've noted gives a good idea of |
| 21 |
the minimum number of inodes consumed as overhead. |
| 22 |
|
| 23 |
-- |
| 24 |
Robin Hugh Johnson |
| 25 |
Gentoo Linux: Developer, Trustee & Infrastructure Lead |
| 26 |
E-Mail : robbat2@g.o |
| 27 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
Archives