|Re: Autocomplete/SearchRequestor Expediency [message #967025 is a reply to message #952470]
||Thu, 01 November 2012 12:27
| Missing name Mising name
Registered: July 2009
a method that is dumb enough to take java.lang.Object as a parameter may not receive suggestions from the ide because it is not the right kind.|
org.eclipse.core.internal.jobs.WorkerPool.sleep(long) 50.1492 3029774 ms (50.1%) 1507
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run() 45.735516 2763120 ms (45.7%) 12
This is a partial visualVm snapshot of the plug-in generating the search suggestions.
Notice that between these two they make up 96% of time. Notice the 1507 times sleep is called.
This is the line that creates the pattern:
pattern = SearchPattern.createPattern("*", IJavaSearchConstants.CLASS, IJavaSearchConstants.CLASS, IJavaSearchConstants.FORCE_IMMEDIATE_SEARCH);
Does eclipse keep a cached list for this particular case?
I can break up the search and cache a list for a dummy project and spread the cost around but before I make changes I wanted to verify what I am doing wrong
[Updated on: Thu, 01 November 2012 17:35]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01667 seconds