Skip to main content



      Home
Home » Language IDEs » Java Development Tools (JDT) » Code Assist lag
Code Assist lag [message #199984] Fri, 01 April 2005 10:26 Go to next message
Eclipse UserFriend
Originally posted by: lapwah.lee.gs.com

On the whole, my experience with Eclipse has been very good but there is
one thing that drives me absolutely crazy. It's enough to make me want to
think about switching to Intellij.

When using Code Assist, Eclipse will time out for a good 3-5 seconds,
sometimes longer. Originally I suspected that it was the network drive
but moving to the local drive has been no help. Upgrading to 3.1 also
doesn't help. My work colleagues experience the same problem.

It's a huge productivity drag when you're on a developing tear only to be
throttled by the IDE.
Re: Code Assist lag [message #200066 is a reply to message #199984] Mon, 04 April 2005 04:57 Go to previous messageGo to next message
Eclipse UserFriend
Hello, could you fill a bug report in JDT/Core
(https://bugs.eclipse.org/bugs/) with a test case or a description of
the completion context (workspace configuration, source code, ...) ?

Code assist is slow for all completions in your workspace ?
Code assist is slow only for some specific completions ?
Code assist is not slow every time for the same completion ?

Thanks,
David

Lap Wah Lee wrote:
>
> On the whole, my experience with Eclipse has been very good but there is
> one thing that drives me absolutely crazy. It's enough to make me want
> to think about switching to Intellij.
>
> When using Code Assist, Eclipse will time out for a good 3-5 seconds,
> sometimes longer. Originally I suspected that it was the network drive
> but moving to the local drive has been no help. Upgrading to 3.1 also
> doesn't help. My work colleagues experience the same problem.
>
> It's a huge productivity drag when you're on a developing tear only to
> be throttled by the IDE.
>
Re: Code Assist lag [message #200115 is a reply to message #200066] Mon, 04 April 2005 06:30 Go to previous messageGo to next message
Eclipse UserFriend
Just to confirm. CodeAssist is meant to answer completions within half a
second normally.
If you are experiencing slower responses on a standard machine, then we need
to get testcases for these.

Things which could also hurt: antivirus ? memory ? VM ?

"David Audel" <david_audel@fr.ibm.com> wrote in message
news:d2qvm5$h2g$1@news.eclipse.org...
> Hello, could you fill a bug report in JDT/Core
> (https://bugs.eclipse.org/bugs/) with a test case or a description of
> the completion context (workspace configuration, source code, ...) ?
>
> Code assist is slow for all completions in your workspace ?
> Code assist is slow only for some specific completions ?
> Code assist is not slow every time for the same completion ?
>
> Thanks,
> David
>
> Lap Wah Lee wrote:
> >
> > On the whole, my experience with Eclipse has been very good but there is
> > one thing that drives me absolutely crazy. It's enough to make me want
> > to think about switching to Intellij.
> >
> > When using Code Assist, Eclipse will time out for a good 3-5 seconds,
> > sometimes longer. Originally I suspected that it was the network drive
> > but moving to the local drive has been no help. Upgrading to 3.1 also
> > doesn't help. My work colleagues experience the same problem.
> >
> > It's a huge productivity drag when you're on a developing tear only to
> > be throttled by the IDE.
> >
Re: Code Assist lag [message #200137 is a reply to message #200115] Mon, 04 April 2005 09:29 Go to previous message
Eclipse UserFriend
Just adding to the other comments: There is a debug flag you can enable
which will then cause eclipse to write out timing data for code assist
to the console:

start eclipse like this:

$ eclipse -debug <optionsfile> [other parameters]

where <optionsfile> is a file containing the following line:

org.eclipse.jdt.ui/debug/ResultCollector=true

Including the output in bug reports helps us to track down the culprit
for slow code assist.

Also see https://bugs.eclipse.org/bugs/show_bug.cgi?id=86579 for another
bug dealing with slow parameter guessing.

-tom

Philippe Mulet wrote:
> Just to confirm. CodeAssist is meant to answer completions within half a
> second normally.
> If you are experiencing slower responses on a standard machine, then we need
> to get testcases for these.
>
> Things which could also hurt: antivirus ? memory ? VM ?
>
> "David Audel" <david_audel@fr.ibm.com> wrote in message
> news:d2qvm5$h2g$1@news.eclipse.org...
>
>>Hello, could you fill a bug report in JDT/Core
>>(https://bugs.eclipse.org/bugs/) with a test case or a description of
>>the completion context (workspace configuration, source code, ...) ?
>>
>>Code assist is slow for all completions in your workspace ?
>>Code assist is slow only for some specific completions ?
>>Code assist is not slow every time for the same completion ?
>>
>>Thanks,
>>David
>>
>>Lap Wah Lee wrote:
>>
>>>On the whole, my experience with Eclipse has been very good but there is
>>>one thing that drives me absolutely crazy. It's enough to make me want
>>>to think about switching to Intellij.
>>>
>>>When using Code Assist, Eclipse will time out for a good 3-5 seconds,
>>>sometimes longer. Originally I suspected that it was the network drive
>>>but moving to the local drive has been no help. Upgrading to 3.1 also
>>>doesn't help. My work colleagues experience the same problem.
>>>
>>>It's a huge productivity drag when you're on a developing tear only to
>>>be throttled by the IDE.
>>>
>
>
>
Previous Topic:JDT's content assist...A question
Next Topic:How does Eclipse decide what files need to be compiled?
Goto Forum:
  


Current Time: Tue May 13 10:18:37 EDT 2025

Powered by FUDForum. Page generated in 0.03240 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top