On Jan 14, 2005, at 12:09 PM, Ben Collins-Sussman wrote:
>> On 2005-01-14 11:08-0800, Arlo Belshee wrote:
>>
>>> + Server: OS 10.3. Subversion v 1.0.2
>>> + Client: Win XP, fast hardware, NTFS. 2 Subversion clients (similar
>>> results with each): Tortoise, svn command-line client. Both are the
>>> ones for
>>> svn 1.0.2.
>>> + Access via svn+ssh. Normally with key agents, but using manual
>>> password
>>> for timing (so I can tell allocate time to a finer granularity).
>>> Total time
>>> similar with keys and passwords.
>>> + Clients run both virus scanner and firewall (standard corporate
>>> config).
>
> I'd also be curious to see what your timings look like using a 1.1.2
> commandline client on a unix-y system.
Here are the timings for Arlo's source (at least the trunk/ directory)
between the 2GHz Xserve the repository is hosted on and my dual G5 box
over gigabit ethernet. Both machines are running subversion 1.1.2.
svn co -q 'svn+ssh://blah/blah/trunk' = 10 mins 7 secs
That puts 2.4 Gigs of stuff in the sandbox according to 'du'. 79997
files and folders.
svn status trunk = 55 seconds
svn up trunk = 10 seconds
So, my checkout times pretty much matches Arlo's. Ten minutes to bring
down 80000 small files doesn't seem too bad I guess, if it's a one time
hit.
However, my update and status times are way shorter. He's seeing about
10 mins each on those. I'm not sure what to make of that. I don't know
if that means there is something terribly wrong with the Windows
version of subversion, or that the disk caching in OS X is way better
than Windows. I've got 1.5 Gigs of ram in my box. During the time
update is running (about 10 secs) I see about 300-600 transactions/sec
and 4-8 MB/sec of activity on my local drive.
Thoughts?
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 19 18:31:17 2005