Re: pristine store design
From: Greg Stein <gstein_at_gmail.com>
Date: Wed, 3 Mar 2010 13:00:09 -0500
I didn't miss any part.
You're optimizing writes, when you should worry about reads.
The DB is always open, so reading and writing to it is "cheap".
I don't care about a scheme to seek to the end of a 16Gb chunk. You're
On Mar 3, 2010 9:45 AM, "Stefan Sperling" <stsp_at_elego.de> wrote:
On Wed, Mar 03, 2010 at 12:24:29PM -0500, Greg Stein wrote:
> You're talking about splitting files for certain filesystems to help with
What Neels and I are trying to get rid of is the need for
You missed the part of not storing data in an sqlite DB which will
Writing the pristine itself is already lockless, and also writing
> Putting data in the file means you have to *open* it to read the data.
The proposed scheme even minimises I/O in case we need only a chunk
Granted, reading an entire huge pristine involves opening a number of
> Again: we are centralizing in order to aggregate data and reduce I/O. Your
This is an archived mail posted to the Subversion Dev mailing list.