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

Re: Best Practices: Performance on Large Repositories?

From: Steve Seremeth <subversion_at_seremeth.com>
Date: 2005-03-18 19:15:14 CET

Followup: this issue has been somewhat resolved.

It seems that if not much else is running on a Windows system that is
using TortoiseSVN or the svn command line interface -- we have been able
to see major performance improvements. Sounds obvious, but please allow
me to elaborate.

We had been seeing 20-30 minute times to "check for modifications" (i.e.
status) when run against the top of our working copy tree of about
11,000 version-controlled files (plus another 44,000 svn control files)
on certain systems. We thought everyone was feeling this pain here, but
that was not the case -- only a few of us. Also, the amount of data in
the working copy is closer to 2 GB on disk instead of the 1200 MB we
thought we had.

Ok - so back to the details (or what we _do_ know). We would regularly
kick off a "Check for modifications" at the top of the tree and see
TortoiseProc just linger around in Task Manager's process list not using
much cpu _at all_. We would see similar things with svn.exe when run at
the command line. When sorting on cpu use, often times the only thing
in the process list taking more (ok, almost all) the cpu was "System
Idle Process". Very frustrating.

On one system, we killed a vmware instance that was lingering around and
got status checks generally down to about 12 seconds a shot -- VERY
liveable performance. We still have a couple systems experiencing very
slow Tortoise/Subversion performance, but clearly it's some other
process on those boxes causing the issue. We have seen McAffee AV
causing pain from time to time, but we have not concluded where the real
devil is. Some of us have Windows Indexing on and some of have it off
with mixed performance degradation.

So while we're not positive what is causing our problems, we are
starting to decide:

1. It's not Subversion related (although it's clear TortoiseSVN doesn't
help with screen draws in Windows Explorer).

2. Subversion is fine performance-wise even with our fairly large

Is there a way to run some sort of debug build under windows to see what
the slowness is (like wait i/o, etc.)? Maybe if it could generate a log
that had timestamps for each part of a transaction?

Thanks for everyone's input.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 18 19:17:52 2005

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

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