Nathan Kidd <nathan-svn@spicycrypto.ca> wrote on 05/17/2005 11:29:38 AM:
> Idea 1:
> A new option /* Nathan dodges Stefan's +6 Bolt of Option-Zapping
> Lightning */ applying to the Show Log dialog could be:
> "Load changed paths later" (or similar)
> Which when selected does a "svn log" instead of "svn log -v".
> After displaying the initial results it then automatically does a "svn
> log -v" and starts filling out the path structures.
> PRO: you get near-immediate feedback, particularly helpful when simply
> choosing a revision number (e.g. for merge)
> CON: duplicating network/server traffic, paths of recent changes may not
> be filled out as quickly
We are using this technique in Subclipse. When we initially load our Log
history it does not contain any path information. As you select a
specific revision, if the path information is not already loaded for that
revision it gets it on demand. On internal repositories you do not even
notice it is doing this. On external, there is a very slight delay.
In Subclipse we did it more to reduce the memory usage. Some people would
run out of memory if we loaded everything at once. This is a Java issue
as it sets a maximum heap size that is relatively low. The point is that
the performance was a lot better than I thought it would be. It is mostly
not noticeable.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue May 17 17:40:21 2005