Community
Participate
Working Groups
Building a project using build 20020314-Win32, when the files are on the network is slow. On a local drive a rebuild (around 700 Java files) on a P2 450Mhz/256MB machine takes 55 seconds. On a network it takes 224 seconds. 132 seconds to delete the output directory and 92 seconds to compile. Deleting the output manually (using Explorer) takes only 32 seconds.
> I measured each operation, and find that it takes 132 seconds to > delete the content of the output directory... Was this with a designated output folder? Or with the .class files in the same folder as their .java file? How did you delete the .class files from the output folder? From a resource perspective in eclipse?
To give you some idea of the performance I see with a workspace on the network... take them with a grain of salt since network performance can be very inconsistent. I've seen 10 second spans when my processor never got over 20%. The workspace is a complete eclipse drop from source... 5910 java files over 52 projects. The rt.jar is on the local machine in both cases. Incremental builds took less than 3 seconds when adding a space to a .java file... less than 1 second in the local workspace, 1.5 - 2.5 seconds in the network workspace. Local workspace: Full build took 4:00 minutes flat with CPU @ 80-100%, free memory bottomed out @ ~48Mb available, down from 102 Mb. Network workspace: Full build took 10:22 minutes with CPU @ 30-50% (with wild swings from 0-85%), free memory bottomed out @ ~56Mb available.
The project was with a designated output folder, not the .class files in the same folder as their .java file. The .class files I deleted using MS Explorer to delete the output folder. I executed these test a couple of times, the difference in times are not too big (+/- 5 seconds). I wrote a small Java application to delete a directory. It takes 40 seconds to delete 47 directories, 500 files. Deleting the same directory from the Eclipse Resource Perspective it takes 47 sec. Deleting it with Explorer it takes 17 seconds.
I changed the batch builder to do nothing but delete the output folder of each project... I don't see anything like the numbers you're getting. It only took 19 seconds to delete the output folders of all 52 projects (8693 class files). When you do a full build, do you see the message "Scrubbing output folder" more than half the time?
Interesting. Yes, at full build I see "Scrubbing output folder" more than half the time.
see http://dev.eclipse.org/bugs/show_bug.cgi?id=10628
Adalbert can you describe your network please? What type is it? Number of users, etc.
Hi Kent, This seems to be a duplicate of bug 10628. Just for your info, We have a Windows NT network, the server is a Solaris box, using a Samba network, to export the ClearCase controlled files. They are around 30 people using the version control, but only 3-5 who are using it from Windows (using Samba). I did not experience any slowdown because of too many users. I always had wait the same amount of time. If scrubbing the output folder can be speed up, as the discussions of bug 10628 suggest it, Eclipse users should be fine with that. I seen your timing. What kind of network you have ?
*** This bug has been marked as a duplicate of 10628 ***
