On Tue, 2005-11-08 at 23:39 -0800, Jim Blandy wrote:
> On 11/8/05, Greg Hudson <ghudson@mit.edu> wrote:
> > They sound like fine semantics. :) I'm just not sure how to make it
> > work offline either.
>
> We could just always store all the properties of all a directory's
> parents somewhere in its .svn subdir. (To keep wc directories
> independent, we'd need to repeat it, even when the wc parent is based
> on the repos parent.) Retch, but seriously, how much space are we
> talking about here? And we know we want the facility.
The problem with space usage on the client side isn't that we have
properties at all, it's that we store file properties for a single
file .... in a single file per file :)
This isn't very efficient space wise, or performance wise, in most
cases, the props are smaller than a disk block.If you do something
"insane", like store svn:eol-style on each file. you end up with the
base props, the working props, 1 disk block each. As we discovered the
hard way, this takes 300 meg out of 960 on a checked out gcc copy, and
to make a long story short, we don't have file-props anymore on the gcc
repository, except where absolutely necessary. We also don't write out
the word "END\n" to files just to represent empty hashes :)
Anyway, back to the issue at hand. Dir-props are pretty efficient,
because there is only one file per dir.
--Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Nov 12 04:20:17 2005