Syntax analysis bogs down editing

I've noticed a very dramatic slowdown in the last few releases of the
EAP in it's syntax analysis. (The time it takes for the little box in
the upper right to go from to a red/yellow/green)

Now, this wouldn't be a problem (you are probably trading speed for
stability at this point =)) but it definitely causes the responsiveness
of the editor to take a nosedive. Typing, highlighting, etc, are all
choppy. Any time I edit it kicks the syntax analysis back in and slows
it down again. (Clicking around/highlighting shows that it's back to
normal once the thing finishes.)

These files are about 2000 lines of code so we're not talking huge here.
It's more noticeable on the larger files, obviously, since it never
'snaps' out of it. I know about ctrl-8 but this is noticeable to some
degree on every file I have. Is there any way for you guys to make it
take less cycles away from the editor's cpu time, or is this stuff still
being performance tuned? It was way better (in that, I never noticed it)
back in the 21X EAPs.

-Greg

4 comments
Comment actions Permalink

We are currenlty working to improve the performance of the syntax analyzer.

This analysis should be interrupted immediately once you've typed smthing,
so it's presence shouldn't affect the typing in the editor.
Do you experience significant slowdown in typing?

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Greg Fodor" <greg@parature.com> wrote in message
news:e07f8b$i48$1@is.intellij.net...

I've noticed a very dramatic slowdown in the last few releases of the EAP
in it's syntax analysis. (The time it takes for the little box in the
upper right to go from to a red/yellow/green)

>

Now, this wouldn't be a problem (you are probably trading speed for
stability at this point =)) but it definitely causes the responsiveness of
the editor to take a nosedive. Typing, highlighting, etc, are all choppy.
Any time I edit it kicks the syntax analysis back in and slows it down
again. (Clicking around/highlighting shows that it's back to normal once
the thing finishes.)

>

These files are about 2000 lines of code so we're not talking huge here.
It's more noticeable on the larger files, obviously, since it never
'snaps' out of it. I know about ctrl-8 but this is noticeable to some
degree on every file I have. Is there any way for you guys to make it take
less cycles away from the editor's cpu time, or is this stuff still being
performance tuned? It was way better (in that, I never noticed it) back in
the 21X EAPs.

>

-Greg



0
Comment actions Permalink

I agree, especially in 228 where every file that was a Component and had over 1000 lines of code. What's the hurry of analyzing the file. I think it's better to analyze the file more slowely and keep the analysis box intact and then replace it with the new analysis after it has finished (may take longer time than now). i.e. lower the analysis thread priority and make the switch of the analysis "domain" more invisible (or better configurable ;-).

Also some strange behaviours i could not do this in some occasions

DoStuff(profile.PhysicalPreferences.Id,0);

(wanted to change to)
DoStuff(profile.PhysicalPreferences.Id,0,0);

But when i hit comma it would be after the rightmost parantesis. (well I've just installed 229 and see if it is handling that case better).

0
Comment actions Permalink

Hello Eugene,

I have the same problem (r#229/VS2003), r# has a significant lag when doing
code analysis while I'm typing. I had the feeling that this was faster for
me in build 227.

Guy

We are currenlty working to improve the performance of the syntax
analyzer.

This analysis should be interrupted immediately once you've typed
smthing,
so it's presence shouldn't affect the typing in the editor.
Do you experience significant slowdown in typing?



0
Comment actions Permalink

It seems to slow down a lot when I press ctrl-space while typing method parameters
and r# is looking for suggestions with every character that I type. So I
don't think it has anything to do with syntax analysis. The solution I'm
currently working on is not large at all (1 project, <200 classes). The
memory usage reported by the statusbar is 28.7Mb and I have a lot of free
system memory.

Hello Eugene,

I have the same problem (r#229/VS2003), r# has a significant lag when
doing code analysis while I'm typing. I had the feeling that this was
faster for me in build 227.

Guy

>> We are currenlty working to improve the performance of the syntax
>> analyzer.
>>
>> This analysis should be interrupted immediately once you've typed
>> smthing,
>> so it's presence shouldn't affect the typing in the editor.
>> Do you experience significant slowdown in typing?


0

Please sign in to leave a comment.