Parse time

Has anyone else noticed this...

I have my autoparse delay set to 300ms, and on earlier builds what this effectively meant was that if I inserted typos or some other bad code then those errors would be highlighted almost instantly with a red underline and the stripe would light up in red.

What happens now is that on the same set of files, it can take maybe 5,6,7 seconds - then in the latest build the "all seeing eye" flickers on and off almost immediately before finally showing me the red/yellow/green file status.

Because of this, I end up waiting for the editor to catch-up and show me the errors or I may have started working on some other area of the file, only to have to go back.

The instant error feedback is much more useful to me than some on-the-fly code inspection.

My guess is that started happening when the background inspections were started.

Any other comments?

7 comments
Comment actions Permalink

This is one reason, why I call the latest EAP builds sloooow.

Tom

0
Comment actions Permalink

No, Mark,
I have also noted this effect and was sure it was because of inspections.
But after making a profiling, it turned out that the inspections consume
only 1/8 time of the general highlighting pass.
So the problem lays deeper in the code, and probably is related to generics
support we are doing now. However the team now works on the optimization of
the most common routines where
generics have put an overhead, so this is going to be corrected in later
builds.
Eugene

"Mark Lee" <no_mail@jetbrains.com> wrote in message
news:20009668.1059030302821.JavaMail.itn@is.intellij.net...

Has anyone else noticed this...

>

I have my autoparse delay set to 300ms, and on earlier builds what this

effectively meant was that if I inserted typos or some other bad code then
those errors would be highlighted almost instantly with a red underline and
the stripe would light up in red.
>

What happens now is that on the same set of files, it can take maybe 5,6,7

seconds - then in the latest build the "all seeing eye" flickers on and off
almost immediately before finally showing me the red/yellow/green file
status.
>

Because of this, I end up waiting for the editor to catch-up and

show me the errors or I may have started working on some other area of the
file, only to have to go back.
>

The instant error feedback is much more useful to me than some on-the-fly

code inspection.
>

My guess is that started happening when the background inspections were

started.
>

Any other comments?



0
Comment actions Permalink

Mark,

When "all seeing eye" appears it actually is drawn upon red/yellow/green
indicator and all your errors ARE in fact already highlighted. There's no
need to wait until the eye disappears. Yes, inspections can find something
that will change green->yellow->red so initial indicator value is not final.
That's why we need that eye. Finally I can't understand why an eye changed
the things to worse since it starts its work only after all usual
information is catched and delivered to you.

--

Best regards,
Maxim Shafirov
JetBrains, Inc / IntelliJ Software
http://www.intellij.com
"Develop with pleasure!"


"Mark Lee" <no_mail@jetbrains.com> wrote in message
news:20009668.1059030302821.JavaMail.itn@is.intellij.net...

Has anyone else noticed this...

>

I have my autoparse delay set to 300ms, and on earlier builds what this

effectively meant was that if I inserted typos or some other bad code then
those errors would be highlighted almost instantly with a red underline and
the stripe would light up in red.
>

What happens now is that on the same set of files, it can take maybe 5,6,7

seconds - then in the latest build the "all seeing eye" flickers on and off
almost immediately before finally showing me the red/yellow/green file
status.
>

Because of this, I end up waiting for the editor to catch-up and

show me the errors or I may have started working on some other area of the
file, only to have to go back.
>

The instant error feedback is much more useful to me than some on-the-fly

code inspection.
>

My guess is that started happening when the background inspections were

started.
>

Any other comments?



0
Comment actions Permalink

Evgueny Vigdorchik wrote:

> I have also noted this effect and was sure it was because of
inspections.
> But after making a profiling, it turned out that the inspections consume
> only 1/8 time of the general highlighting pass.

Do intentions kick in while IDEA is still doing its other legitimate
business?

If they don't, ignore the rest of this message.
If they do :
- This could be a problem because users can add hundreds on intentions
through plugins.
- There should be a way to prioritize intentions, and tell the system,
"this intention is heavy, put it at the end of your todo list".
- In absence of explicit priority, a nice feature would be for IDEA to
put all user's intention at the end, watch them run, and reorganize
them, based on their averate execution time.

Alain

0
Comment actions Permalink

Alain Ravet wrote:

Evgueny Vigdorchik wrote:

> I have also noted this effect and was sure it was because of
inspections.
> But after making a profiling, it turned out that the inspections
> consume only 1/8 time of the general highlighting pass.

Do intentions kick in while IDEA is still doing its other legitimate
business?

If they don't, ignore the rest of this message.
If they do :
- This could be a problem because users can add hundreds on intentions
through plugins.
- There should be a way to prioritize intentions, and tell the system,
"this intention is heavy, put it at the end of your todo list".
- In absence of explicit priority, a nice feature would be for IDEA to
put all user's intention at the end, watch them run, and reorganize
them, based on their averate execution time.


In the previous life, I have been doing video compression stuff. Got a
patent pending on stuff like that :)

Cheers,
Dmitry

P.S. I am in vacation anticipation mood these days :)
--
Dmitry Lomov
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0
Comment actions Permalink

Dmitry,

>P.S. I am in vacation anticipation mood these days :)
>

When will you be in "vacation activated" mode? :)


Alain

0
Comment actions Permalink

Alain Ravet wrote:

Dmitry,

>>P.S. I am in vacation anticipation mood these days :)
It should actualy read:
>>P.S. I am in vacation anticipation mood these days]]>
:)
>>


When will you be in "vacation activated" mode? :)


Saturday, saturday, lovely saturday :)

Cheers,
Dmitry
--
Dmitry Lomov
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0

Please sign in to leave a comment.