Community
Participate
Working Groups
I have noticed that over time, I use fewer and fewer of Eclipse's features, because it takes longer to use them than for me to do things manually. For example, ctrl-space will often take over a second to bring anything up. I find it faster to type myself, so I do not use code completion. Similarly, ctrl-shift-T (search for class) can take over 5 seconds to display, which renders it next to useless for me. Holding down ctrl to get the hyperlink-to-declaration will hang the entire editor window for several seconds, and then when I do click on something it will often be where the mouse was a second or so ago, which makes it open the incorrect page. It also often requires several seconds of constant CPU usage to open the new editor window, making me even more frustrated when it got the wrong one. I have a 1.8GHz machine with 1GB of RAM. The projects I work on aren't that large, maybe 1000 classes or so, with 30 or so dependent libraries, so I don't see why so much functionality should become unusable.
Kesley, we did some performance optimizations especially in the area of open type and code assist. Did you encounter this behaviour with the latest build of the 3.0 stream or are you using plain 2.1.1.
This is 2.1.1, I have not used 3.
Can you please give 3.0 M4 a try and let me know if you still see the performace problems.
Closing as works for me. We will not do anything for 2.1.x.