I have performance problems with subclipse, but I suspect it is more to
do with my setup than subclipse itself.
I run eclipse/subclipse on a windows machine, with my project files
actually stored on a separate fileserver on the LAN, which is a Linux
box, and with the SVN server on a third machine also within the LAN.
This is very slow not only because of the extra hop when doing svn
operations (the files go from the SVN server to my windows machine and
from there to the fileserver), but also because samba performance on
Linux is pretty slow, particularly when dealing with large directories
of many small files.
If I use the command line client from the fileserver to do my SVN
operations, that is an order of magnitude faster, but I think that is
because there isn't the extra network hop, and also it doesn't need to
deal with Samba issues.
If you have a similar setup (which I don't imagine is uncommon), that
could be the cause.
Performance when my files are on the same machine as eclipse seems much
the same as it does with the command line client. So I don't think
subclipse is the issue (in my case)
> The difference in speed between Subclipse and the command-line svn
> client, when working with projects that contain huge numbers of tiny
> files, is at least an order of magnitude, possibly two. If anyone
> knows of a way to bring Subclipse's performance up closer to what it
> it apparently should be capable of, I'd appreciate tips... and would
> suggest adding them to the FAQ.
> Meanwhile, command-line is a workaround... just not as elegant.
> "... Three things see no end: A loop with exit code done wrong,
> A semaphore untested, And the change that comes along. ..."
> -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish
Received on 2008-10-06 06:05:11 CEST