Marvin Toll <tollm@dteenergy.com> wrote on 09/12/2006 03:07:23 PM:
> Our topology is as follows:
>
> Solution Topology (versions are current as 9/1/2006):
> Server
> MicroSoft Windows 2003 Enterprise Ed. SP 1
> Subversion v. 1.3.2
> svnserve.exe
> Client (2 Gb RAM)
> Eclipse IDE v. 3.2
> Callisto Plugins (excepting ?C and C++ Development?)
> Subclipse Plugin v. 1.1.5 (Subversion client)
> Jad v.1.5.8 (Decompiler)
> Jadclipse Plugin v. 3.2.2 (For Jad)
> FindBugs v. 1.0 (Static code analysis)
> The projects on the client are as follows:
> Open projects include .svn directories
> #1 = 1.12Gb
> #2 = 118Mb
> #3 = 435Mb
> #4 = 274Mb
> Closed projects use SourceForge server
> #1 = 710Mb
> #2 = 248Mb
> #3 = 2Mb
> #4 = 60Kb
> #5 = 8Mb
> The performance within Eclipse is debilitating. We are trying to isolate
> variables and determine if performance problems are simply associated
with
> project size in Eclipse, open vs. closed projects make a differnece,
and/or
> if Subclipse is responsible. (Obviously, if we eliminate .svn files are
> size diminishes by 50%.)
>
> We are also moving to a Linux server. However, based on both
client/server
> Task Manager statistics our performance problems appear to be client
side.
> (We allocate -vmargs -Xmx512M heep, have automatic build turned off, and
do
> not Organize Project on startup.)
>
> As an example, it can take twenty minutes to open Eclipse.
>
> Has anyone had experience with projects of this size? What was that
experience?
We had someone else post a month or so ago with similar questions. We
made some optimizations in Subclipse 1.1.3 that he said made a big
difference, especially on startup. We also had additional enancements in
the two subsequent releases. We have more still on trunk but these would
effect things like refreshes after builds not startup.
I do not think our code is doing a lot during startup any more. We
certainly do not make any calls into Subversion API's.
Subversion is more effected by number of files and folders than by the
size. There is one exception and that is if your files have all had their
date/times changed but were not otherwise changed. This forces Subversion
to do a complete diff of the file to determine that it is unchanged.
Again, this should not effect Eclipse startup.
Subversion 1.4 contains a lot of significant performance improvements to
working copy size and management. Again, will not effect Eclipse startup.
The Subversion server platform will not effect performance. svn://
protocol is fastest and has less files in the working copy.
If you do Team -> Disconnect on all your projects, but do not delete the
.svn metadata folders. Does this change performance? If it doesn't, then
I do not think Subclipse is the issue. If it does, then we probably are.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Sep 12 21:27:48 2006