Very slow typing response in 1866

I can't pin it down to anything specific yet, but I'm finding typing pretty much in any code to be very sluggish. Sometimes with 1 or 2 second delays. No threaddumps or exceptions are being generated.

7 comments
Comment actions Permalink

Ok, it was having the structure view open. Guess its better to keep it undocked for now.

0
Comment actions Permalink

I have noticed the same behavior. As a workaround I use the File Structure Popup. It's Ctrl+F3 by default.

0
Comment actions Permalink

If you need to see file structure, it's better to use Ctrl+F12 shortcut (press it twice to see all inherited members). You will never forget to close structure view, if you use this shortcut.

Best regards,
Alexander Podkhalyuzin.

0
Comment actions Permalink

Yes, I typically use Ctrl+F12, if only because its easy to search. But sometimes I'm browsing unfamiliar code.

Out of curiosity, what is different with the scala plugin from java that this uses so much resources?

0
Comment actions Permalink

Same difference as between scalac and javac. Maybe our analyzer is less effective then scalac, but they both is much less effective then javac. Mainly it's because of language complexity. I hope It won't be more slowly then now, but I can't guarantee it (because type system isn't implemented yet).

Best regards,
Alexander Podkhalyuzin.

0
Comment actions Permalink

Yes, of course there is much more work in processing scala. I wondering why specifically the structure view has an impact. Does that imply that some work gets deferred if that view is closed?

0
Comment actions Permalink

Even Ctrl+F12 isn't really fast as you can see. So freezings with opened structure view is on same amount of time. It's possible that it's fixable, but I'm sure that I won't check it in the nearest future.

Best regards,
Alexander Podkhalyuzin.

0

Please sign in to leave a comment.