On Wednesday 24 January 2007 00:24 Gunter Ohrner wrote:
> Sorry to bother you again... ;)
NP.
> While testing the partial commit fix (and commits in general) I noticed an
> extreme performance degradation. ...
> fsvs did not seem to prune any path excluded by my partial commit filter.
> However, even for a full commit this performance would not be acceptable,
> ie. currently fsvs' usage for it's ultimate goal - managing whole
> software installations - is rather limited. :-(
I cannot reproduce that.
On my (limited) test fsvs skipped all directories, going only through those
that had marked children.
Of course, if you give a directory as parameter, it goes through all its
children, too.
> Why does fsvs touch all directories during a commit, even if nothing has
> changed locally? Is this some kind of "bug", or is it required by svn's
> architecture if you want to handle commits correctly?
No, it shouldn't.
> Client was a Core Duo 2 notebook, the server was a Athlon64 3800+, both
> where connected via an 4 MBit/sec ADSL link with 40 ms latency. Both
> systems are running Debian Linux i386 with subversion 1.4.
>
> The repository contains parts of my home directory and its current
> revision consists of 12455 directories and 70067 files at the moment.
I'll take a few more looks.
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
