[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] Re: Another go at a patch for SVNFolderStatus

From: Will Dean <will.dean_at_indcomp.co.uk>
Date: 2004-10-29 22:46:34 CEST

At 15:38 29/10/2004 +0100, you wrote:

>I agree with that. I have just said in the ReadMe for nightlies that
>even if TSVN is untested, it is based on a stable SVN release so it is
>safe to use on live data. We do not want to risk making repository
>access unstable. The main purpose of the nightly build is to allow
>testing of TSVN features.

Yes, I think I agree with this too, in general. It's just when we're at
the current stage in the SVN release cycle, when there will be no big
release until locking is implemented (which could be ages), it seems like
it might be hard to get mere performance issues into a SVN release.

The problem is that SVN can actually suffer terrible perf problems in its
official releases, and these can bleen through into TSVN. TSVN 1.0.8 was
incredibly slow, and was the latest official TSVN release for a long
time. This was because Stefan had forgotten to apply a SVN patch before
building it.
(This patch had been in previous TSVN releases)

So TSVN hasn't always (or perhaps even generally?) been built off
un-patched SVN releases, and maybe that's just inevitable, though clearly

>Will has been doing sterling work on tracking down inefficiencies and
>slow down factors, which will ultimately benefit everyone, but I am not
>sure we should increase the risk exposure of all Beta testers, even if
>the patch seems safe.

Personally, I would much prefer us to patch TSVN to avoid this particular
perf bug, but I'm failing to convince Stefan that my avoidance technique is
safe. (Though the ball is currently in his court to tell me why it isn't! ;-)

Of course, it actually matters less to me than to anyone else, as I'm
cheerfully running a build with all these patches in.

Maybe I should fork the whole lot (apr, svn, etc), apply my performance
patches where I see fit, and just publish that as a 'racing version', for
people to take if they trust me, and not if they don't...

>Having 2 builds (released SVN and patched SVN) sounds like a difficult

Dreadful idea - definitely not.



Will Dean - Industrial Computing Ltd
will.dean_at_indcomp.co.uk - http://www.indcomp.co.uk/
Elmcroft, Wyke Road, Gillingham, Dorset, SP8 4NG, UK
Tel: +44 1747 831001    Fax: +44 1747 824783
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Oct 29 23:59:36 2004

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.