>> In a random mcz file from my cache (Kernel-721.cwp):
>>
>>      15     package
>> 1482380     snapshot.bin
>> 1407480     snapshot/source.st
>>  243499     version
>>
>> These are byte counts, so the ancestry data (in "version") takes up about
>> 8% of the total. If we really want to make these files smaller, we'd do
>> better to get rid of the redundancy between snapshot.bin and
>> snapshot/source.st.
>
>
> I thought that the issue was not file size but in-image footprint.  What do
> others think?

MC has 3 limitlessly-growing aspects causing increased degradation and
scaling issues.  1) The in-image ancestry, 2) the allFilenames cache
size (this is the Numero UNO thing our trunk server spends time
doing), and 3) the repetition of code in .mcz files packages wastes
quite a lot of space.  Morphic is probably the largest, its 582
versions in trunk consuming 857M today.  Total size of packages in
/trunk is currently 3.1G.