Funny thing is that for some repos, the file will shrink even further if you
re-run the command a 2nd time.
-Original Message-
From: Richard Hipp
Sent: Saturday, November 28, 2015 1:52 AM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] Why does the repo file grow over
On 11/27/15, sky5w...@gmail.com wrote:
> Nice, I just recovered 50% file size using:
> fossil rebuild --compress-only
> I had only ever used fossil rebuild and vacuum's?
> Thanks for heads up.
>
Note that this works with the "all" command too:
fossil all rebuild
On Nov 27, 2015, at 5:11 PM, Richard Hipp wrote:
>
> On 11/27/15, Warren Young wrote:
>> So, what did that fix actually do? What was taking up the extra space,
>> which VACUUM did not find?
>
> The command does extra delta-compression.
Would a correct tl;dl
Nice, I just recovered 50% file size using:
fossil rebuild --compress-only
I had only ever used fossil rebuild and vacuum's?
Thanks for heads up.
On Fri, Nov 27, 2015 at 5:11 PM, Warren Young wrote:
> On Nov 27, 2015, at 3:06 PM, Richard Hipp wrote:
> >
> >
On Nov 27, 2015, at 3:06 PM, Richard Hipp wrote:
>
> On 11/27/15, Warren Young wrote:
>> Why is my year-old clone so much larger than a fresh clone?
>>
>> And yes, I did re-VACUUM the repo file before posting. That did shrink it
>> considerably, from about
On 11/27/15, Warren Young wrote:
> So, what did that fix actually do? What was taking up the extra space,
> which VACUUM did not find?
The command does extra delta-compression.
Fossil does not store the complete text of every version of every
file. Instead, it tries to store
On 11/27/15, Warren Young wrote:
> On Nov 27, 2015, at 5:11 PM, Richard Hipp wrote:
>>
>> On 11/27/15, Warren Young wrote:
>>> So, what did that fix actually do? What was taking up the extra space,
>>> which VACUUM did not find?
>>
>> The
> Another research problem: Current, Fossil only delta-compresses
> versions of the same file. Enhance --compress so that it detects
> different files that happen to share a lot of content and delta
> encode them against one another.
Idea for a multi-phase process to hopefully avoid the
On 11/27/15, Warren Young wrote:
> Obviously checking in new versions adds data to the repo file.
>
> My question is subtler than that. I noticed while participating in another
> thread here that a fresh clone from http://fossil-scm.org gives a repo file
> that’s about 36 MiB,
Obviously checking in new versions adds data to the repo file.
My question is subtler than that. I noticed while participating in another
thread here that a fresh clone from http://fossil-scm.org gives a repo file
that’s about 36 MiB, but my preexisting clone of the repo is 65 MiB.
Why is my
10 matches
Mail list logo