Description Gary Mazo 2002-03-18 13:51:10 EST

With a large number (150-200) of projects in the workspace, some essential 
operations ("Open type to hierarchy", "debug step", "switch perspective", etc.) 
slow down to 5-10 minutes for a single operation to complete. At this point the 
state of the workbench is not useable and it is not always possible to predict 
which operation will cause the wb to lock-up.

This is reproducible on all recent "stable" levels of Eclipse 2.

Eclipse V2 - Usability/Performance Comparision

Machine Details Table

Name	                Speed	Memory	Operating System
Pavan K Immaneni	550 MHz	576 MB	Win NT (SP 5)
Gary Mazo(Home)	        1.3 GHz	392 MB	Win 2000
Kent Hawley(Work)	850 MHz	512 MB	Win 2000



Operations Table
 
No Operation                                     Pavan      Kent(H)   Gary(H)
----------------------------------------------------------------------------
1  Bring up development workbench	         25-30 min  6-7 min   3-4 min 
2  Bring down workbench	                         1-2 min    1 min     Fast
3  Opening an editor on a Java file	         3-4 min    Fast      Fast
4  Opening plus-signs in Packages view	         2 min      Fast      Fast
5  Open Type to Hierarchy	                 20-25 min  4-5 min   4 min
6  Go to Type	                                 25-30 min            8 sec
7  Go to Package	                         25-30 min            2.5 min
8  Change preferncs(eg.Eclipse Home variables)   35 min     9-10 min  n/a
9  Change the JRE from JDK1.3 to JDK1.4	         45 min	    10 min    n/a
10 Re-build All	                                 20-25 min  8-9 min   3 min
11 WB Debug start-up			         <1min
12 Debug step		                                    8-10 min  5-6 min