On 8/6/18, Richard Hipp <d...@sqlite.org> wrote:
> On 8/6/18, Philip Bennefall <phi...@blastbay.com> wrote:
>> Do you have any recommendations for something we could try in order to
>> get more information, or would you suggest that we switch to another
>> DVCS if we need to store files of these sizes?
> Regardless of the problem, I don't think *any* DVCS is appropriate for
> storing gigabyte sized binary files.  You should look into a
> centralized VCS such as subversion, methinks.

Further information:

Fossil was written for the purpose of managing the SQLite project.
The primary SQLite Fossil repository contains about 5.8 GB of content
when fully expanded, but that is compressed down to 92 MB.  In other
words, the whole repository spanning 18 years of development and 20K
check-ins and 78K artifacts is less than 1/10th the size of just one
of your files.

The largest uncompressed artifact in the SQLite repo is 19 MB and the
median uncompressed artifact size is 42 KB.  With compression the
largest artifact is 1.8 MB and median artifact size is a mere 152

I analyzed a bunch of other Fossil repositories, and they all mostly
have similar stats.  Except, usually the maximum uncompressed artifact
size is about an order of magnitude less than 19 MB (SQLite is has a
few exceptionally large artifacts) and in the case of the SQL Logic
Test repository, the median artifact size was 1.5 KB.

D. Richard Hipp
fossil-users mailing list

Reply via email to