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

Re: Bad performance with large binary files

From: Folker Schamel <schamel23_at_spinor.com>
Date: 2004-04-07 17:24:20 CEST

> On Wed, 2004-04-07 at 05:32, Branko ─îibej wrote:
>>On the other hand, if you're saying that it takes Subversion about 3
>>minutes to figure out that a 290 MB file has changed on disk, then
>>that's about as expected,
> Well, 'svn status' shouldn't be using brute-force comparison very
> often. It should be looking at timestamps and filesizes as a first
> resort, giving a near-instantaneous answer. I wonder why those aren't
> working for Ralf...?

I think I've read that after a revert or after undoing changes
the comparison is always necessary for this file.
Is this correct?

If yes, this means somehow a "degeneration" of the wc
(I do a fresh checkout because of this from time to time,
because the wc is quite large, and svn status takes a long time).

Is it possible that after one comparison the new timestamp
is stored in the admin directory,
so that after such an undo only for the first status
a comparison is necessary?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 7 17:25:06 2004

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

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