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

RE: Svn scaling issue

From: Arlo Belshee <arlo_at_criticalpath.com>
Date: 2005-01-14 20:28:23 CET

All times were for directory operations: I told it to commit the top-level
directory (and thus the whole subtree). A commit of a single file is as fast
as one would expect.

Times are very similar between Tortoise and command-line. However, some
actions are faster on the command-line, especially those where Tortoise
wants to display all affected files (eg, commit with many changes).

Note: all previous file / directory numbers are approximate, and some of
them were for the entire working copy (not just the branch upon which I'm
working at the moment). I was estimating the amount of stuff in the .svn
folders and discounting it. The total size of the branch on which I'm
working, including svn folders, is now: 120,000 files, 5 GB total size,
18,000 directories.

In addition to the trunk, we've got two branches (both made with server-side
svn copy commands, and then modified slightly from there). I have not
attempted any operations on the entire tree, except the original checkout.
The lock times make such operations infeasible.

Arlo

-----Original Message-----
From: kfogel@newton.ch.collab.net [mailto:kfogel@newton.ch.collab.net] On
Subject: Re: Svn scaling issue

> ...

Also: How many files total?

> ...

Well, for example, in Operation 2, we need to know whether you
targeted the commit at that one file, or just told TSVN to commit all
changed files, and let it find them? (I don't know the TSVN interface
for this, but presumably these two different operations are
supported?)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 14 20:47:14 2005

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