sussman@gmail.com wrote on 08/28/2006 09:57:43 AM:
> On 8/28/06, Daniel Berlin <dberlin@dberlin.org> wrote:
>
> > The report from the one person who has ever tried it with large files
> > was that it sped up commit times from 45 minutes to less than 5 ;)
>
> I don't think that this is rocket science which requires testing. :-)
> Of course, if you just insert new data directly into the stream
> without trying to deltify it, it's gonna be way way faster.
>
> What's tricky here is coming up with a design. Should the svn client
> be magically deciding when to deltify or not, based on some heuristic?
> Or should it be controlled by the user via switches or
> config-options? We have a really long standing issue filed (like...
> years old) about giving users the option to toggle compression on the
> fly (something akin to 'cvs -zN'). Is that the interface we want?
I would like to an svn: property used for this so that is not something
that has to be entered into configuration files (with the exception of
auto props to set the property in the first place).
Perhaps the property could be named something like "svn:delta" or
"svn:deltify" with values of "none" and "normal". This would allow us to
introduce specialty algorithms later if we wanted to add custom algorithms
that worked better on certain file types.
Another option I could see would be to somehow base it on the mime type,
but that would push virtually all of the configuration into the
configuration files, which I do not think would be a good idea.
Is svn import doing deltification? If so, if the new svndiff1 compression
is available perhaps it should always just skip the deltification?
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 28 16:28:18 2006