On Tuesday 04 November 2003 10:01, C. Michael Pilato wrote:
> kfogel@collab.net writes:
[snip]
> 3. Never do deltification of any sort in the filesystem code, and
> create an out-of-band compression command that can be run as a
> post-commit hook.
>
> > (2) looks like a wonderful solution; the only thing I'm not sure of is
> > how to do it inside an Apache module. Does anyone know?
> >
> > I assume that (1) would involve a repository config option for the
> > file size. Note also that we used to have an 'svnadmin deltify'
> > command and could easily get it back (see r3920), so (1) may not
> > actually be as much work as it looks like. Those who don't want to
> > run the cron job would just set the size limit to infinity, and always
> > get deltification.
>
> (3) looks simple, involves no repository configuration option, and
> removes all the deltification overhead from the commit process
> itself. O(1) commits, finally.
>
> You have my vote. Subversion chants the "disk is cheap" mantra all
> over the place. If we really believe that, it won't hurt to stop
> deltifying in-process and start doing it in the hooks, even adding the
> exact command-line for running the 'svnadmin tunefs' (or whatever)
> command necessary in the post-commit.tmpl template.
If I understand how this works correctly, this 'svnadmin tunefs' wouldn't
interfere with normal repository operation, correct? If that's true then I'd
say it's not a lot to ask to run this in the post-commit process or as a
cron-job. However, if it does interfere, I would -1 this. I would have to
agree with Jack in that this should be site-friendly and 'global development'
friendly.
Cheers,
John
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 4 22:41:43 2003