Community
Participate
Working Groups
Release 2.1 is slower than I would like when performing a command-space on my TiBook 667/1G/ 48G. It can take two seconds for the context menu to appear in a case like: String foo = new String(); String bar = foo.<cmd-space here> Similarly, RS_<cmd-space> brings up a pick list of 95 possible classes. This takes about two seconds. RS_Evidence e=new RS_Evidence(): e.<cmd-space> also takes about two seconds. That class has 121 methods. It takes about a second and change to do the same on a class in the same package (RS_Phone_Number) that has only twelve methods. So, it does not appear to be linear in the number of classes or methods, at least for under a hundred or so choices. There also appears to be some level of caching going on, as the second time through, it appears in roughly half the time. I still believe that this menu should appear effectively instantanously, so it might be worth a profile. I have not made any changes to eclipse or its startup parameters since installing it, though I do have a number of projects in my workspace that have moved forward from 2.0.1, M3-M5, and the RCs. Since there are fifty of them, I would rather not delete and recreate them unless there is reason to believe it will help.
Can you try this in a nightly build? There have been some performance improvements on the Mac recently that did not make it into 2.1. Thanks.
Tried it with 20030422, and got similar results, though it did feel a bit snappier. (I believe that the code insight method lookup should be a very fast action, as it is something that we want users to do several times per line of code. The ideal would be an effectively instataneous (1/30th of a second or so) response to cmd-space, but I am not sure that is possible.) I noticed it hitting the disk the first time that I executed String foo=new String(); foo.<cmd-space> which took roughly two seconds. I then hit it again, and it took a bit under a second, without a disk hit. This seemed borne out by tests with JDOM Element and Attribute classes, where it took about a second to respond with a list of methods. I will try the RS_ examples at a later date to see what has happened there.
I tried this with 20030520, and saw improvement. It still takes several seconds between hitting cmd-space and seeing the popup menu, though, and still feels draggy. I am impressed with the speed optimizations we have seen thus far, but I believe that this still needs attention. I am impressed with the visible changes seen with 29642, though, so I have a great deal of hope.
I just tried this on a G3 800Mhz and on a G4 1.25Ghz dual, they both are accepted for me after the first attempt. It comes up in 1 second or less. For the first atempt, there is a cache being build, which is not part of SWT.
