> -----Original Message-----
> From: Ashod Nakashian [mailto:ashodnakash...@yahoo.com]
> Sent: woensdag 4 april 2012 13:28
> To: Greg Stein
> Cc: dev@subversion.apache.org
> Subject: Re: Compressed Pristines (Summary)
>
> >________________________________
> > From: Greg Stein <gst...@gmail.com>
> >My vote is compress for files > N bytes (and store on disk), and stick
the
> others into a new pristine.db. Maybe compress before inserting into
Sqlite.
> Not sure. Add a few heuristics for skipping compression on certain files
> types.
> >Shouldn't be too bad to start with that.
> >Cheers,
> >-g
> >
>
> I feel this is indeed what we're closing on, at least for an initial
working demo.
> But I'd like to hear more agreements before committing to this path. I
know
> some did show support for this approach, but it's hard to track them in
the
> noise.
>
> So to make it easier, let's either voice support to this suggestion and
commit
> to an implementation, or voice objection with at least reasons and
possibly
> alternative action. Silence is passive agreement, so the onus on those
> opposing ;-)
+1
The combination of some compression (gzip or plain deflate), maybe some
specific uncompressed files and the small files in SQLite sounds good.
I think the cutoff point for SQLite should be below what we can have in
memory as we can't keep database transactions open to back up streams. 32K
(and a few times higher) should be safe to read in memory at once.
Bert
