Re: Compressed Pristines (Design Doc)
2012/3/25 Branko Čibej <brane_at_e-reka.si>:
> On 22.03.2012 17:01, Branko Čibej wrote:
>> On 22.03.2012 16:50, Daniel Shahaf wrote:
>>> Branko Čibej wrote on Thu, Mar 22, 2012 at 16:37:24 +0100:
> Based on these observations, it's clear that the implementation should
> proceed as follows:
> Step 1: Just compress the pristine files, do not use any packing. This
> gives a 60% decrease in disk usage in the HTTPD case, but even if the
> decrease is only 30%, it's still worth the effort.
> Step 2: Store small (for some definition of "small") compressed pristine
> files in a SQLite database. In the case of HTTPD, this gives an exter up
> to 90% savings in disk usage, but this is a very specific test case and
> it's hard to guess what kind of gain we'd get on average.
Makes sense for me. In that case we also benefit on performance (in
case sqlite blob API has acceptable performance)
And IMHO "small" should be really small (up to 4k) to prevent wc.db
growing in size.
Received on 2012-03-26 11:53:56 CEST
This is an archived mail posted to the Subversion Dev