Wednesday, December 12, 2012 5:44 AM
I'm using TFS 2012 and the Team Explorer Plugin for
Eclipse in TI's Code Composer Studio Version 5.1. I love the new feature to
work 'offline' (Location = local), but with this setting the compare function
gets incredible slow (~0.5 second per file), what makes it useless for
comparing larger directories.
That the same functionality could be much faster,
demonstrates Microsoft Visual Studio: There, comparing directories shows its
results almost instantly...
Is this a plugin problem in general or ‘just’ an unfortunately
combination of Eclipse version and TEE?
Is there a way to speed up?
- Edited by Stéphane Peter Wednesday, December 12, 2012 9:37 AM
Thursday, December 13, 2012 2:58 PMModeratorWhat are you comparing to? Latest? Workspace version?
Friday, December 14, 2012 1:59 PM
Usually, I compare a local folder with a version on the server.
To imagine the dimensions, I made a "compare performance tests" on a little directory containing 41 header files:
server(latest) <-> server (change set) <2 s
local <-> server (latest) 20 s
local <-> local 38 s
Monday, February 04, 2013 4:14 PM
Any update on this?
My customer has this issue as well (compare local with server). Witin VS the compare is much faster.
Tuesday, February 05, 2013 5:36 AM
Therefore, we decided to uninstall the Eclipse Plugin and only use MSVS for TFS access.<o:p></o:p>
Wednesday, February 06, 2013 2:56 PMOwner
Hey Stéphane - really sorry to hear this. Can you let me know what the scenarios you had been hoping to use Eclipse for and I can take a look again at the perf?
If this for folder compare in Source Control Explorer, doing an Eclipse project sync or something else?
Currently, Team, Sync should be very fast as it is actually doing some special tricks there to improve performance. Comparing a local file with a version on the server should be very fast also. We could definitely improve the logic where we are doing a folder compare in Eclipse with a specific version on the server - but to be honest this wasn't something that we saw people doing a lot so hadn't invested a huge amount in for the 2012 release so the logic is pretty much unchanged from 2010.
There is also the potential for perf issues if doing large local workspace operations against the same local workspace in VS and Eclipse at the same time. While this works, the two processes fight for contention of the locks surrounding the local workspace files and one process typically looses a lot which slows the performance of that one down while the other is working. I'm wondering if we have an issue here as that local <> local case you mention above is really confusing to me.