Very, very poor Performance

Hi,

I have created a new project. I´ve added the lwjgl-libs (http://java-game-lib.sourceforge.net/).

Code complition and error parsing of files are very, very slow now. Sometimes Idea freezes, when I try to code complete some methods.


The lwjgl-lib has some classes with many native, static methods...

Any suggestions?

0
5 comments
Avatar
Permanently deleted user

are you using any plugins? I've notice a considerable slow down when I add the inspection gadgets plugin. Not that the plugin isn't good, it just does a lot.

0
Avatar
Permanently deleted user


I've found that InspectionGadgets is best used with a strictly limited set of inspections turned on for interactive use, and a lot more turned on for batch use. Basically I only turn on inspections interactively if they are ones that I wish to fix immediately whenever I see them, and which can't be batch-fixed from the inspections panel. Examples of these include naming conventions, assignment to method parameter/for-loop parameter, and Object/String comparison using == rather than .equals(). Inspections that can be fixed in batch (unnecessary parentheses, string literal as arg to .equals()) and inspections that I want to keep an eye on, but don't necessarily wish to fix immediately (method and class metrics, use of "break" and "continue", magic numbers, collections without initial capacity), I disable for interactive display. With appropriate choices like this, I think you'll find InspectionGadgets performance is a lot more reasonable, without sacraficing too much power.

--Dave "and yes, I will get around to doing performance tuning" Griffith

0
Avatar
Permanently deleted user

I really hope you don't think I was bashing your plugin. It's a wonderful contribution. It just has to do a lot of work which takes time.

0
Avatar
Permanently deleted user

On our (very) large project, performance of every facet of the IDE has become unacceptably slow. Debugging is especially bad, as every "step over" seems to incur a massive performance hit. Last week I went back to 3.0 and haven't looked back (or rather, ahead) since.

0
Avatar
Permanently deleted user

Kirk Woll wrote:

Debugging is especially bad, as every "step over" seems to incur a massive performance hit.


Why not vote for bug 14855?
http://www.intellij.net/tracker/idea/viewSCR?publicId=14855

0

Please sign in to leave a comment.