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

Re: ideas to make svn update faster.

From: Folker Schamel <schamel23_at_spinor.com>
Date: 2005-05-08 19:31:03 CEST

Philip Martin wrote:
> Folker Schamel <schamel23@spinor.com> writes:
>>And Tortoise queries the wc status non-recusively, which then would
>>have to go up to root all the time instead of a single file read,
>>as already explained by Philip.
>>Which translates into multiple times slower.
> It will make it slower, but not multiple times slower. Non-recursive
> status already reads entries files for immediate subdirs and the
> immediate parent.

Immediate subdirs also in case of the status of a file?

> It also does a lot more than just read entries
> files. However changing it to read entries files all the way back to
> the root must, in general, make it a bit slower.

Of course the actual costs depends on your particular situation.
It is pure speculation, but for example in our particular case
we have a quite deep directory structure (and not too many
immediate sub-dirs), and so I suppose Tortoise would be really
multiple times slower.

But what I really wanted to point out:
As far as I know, currently the costs depend only _locally_ on
the project directory structure. But then it would depend on the
tree depth of the _global_ structure of the project.
Which I consider as bad scaling behaviour for large projects,
because it is somehow a change from O(1) to O(log project_size).
Maybe the wording was choosen badly, but this is what I wanted
to express with "multiple times slower".

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 8 19:31:56 2005

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.