Why do Visual Studio and Eclipse spend hours "updating workspace"?
On accepting the the latest changes, a colleague had to wait for an hour with a "Progress Information" dialog containing "Accepting changes" and "Updating workspace...". At the same time (using Resource Monitor) we could see that the .itemdata file for every file in RTC was being read. 1) Why does it do this and 2) why does it take so long?
Visual Studio 2012, RTC 4.0.4 |
One answer
Hello Eddie, could you provide more detail around the workflow? How was the workspace originally loaded? Why is there swapping between the Visual Studio and Eclipse clients? Sonia Comments
Eddie Breeveld
commented Jan 31 '14, 10:42 a.m.
Hi Sonia,
I will try to reproduce the error by loading a workspace with eclipse then switching over to the Visual Studio client.
I tried this with a workspace containing ~84K files and ~37K folders. After selecting the workspace in Pending Changes to accept incoming changes, the "Updating changes" dialog remained open for ~5 mins, then accepting changes took 5 mins. I tried this with a 4.0.6 candidate Eclipse and VS clients.
Eddie Breeveld
commented Feb 06 '14, 10:45 a.m.
110 K files, 24K folders, and about 35 Gigabytes. The jazz server is on a different continent and we get less than 30 Mbit/sec data rate, mostly limited by the data rate out of our local office. 10 threads (that's the only load option I know about!).
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Same problem in Eclipse. It says it's "Recomputing pending changes".
Seems to be caused by swapping between Eclipse and RTC.
Sorry, I meant to say that it seems to be caused by swapping between Eclipse and Visual Studio RTC clients.