Performance problems with IDEA Follow
I seem to have performance problems with IDEA with large
projects and specifically when the files become large (>3000 lines) even with all the smart type Code completion off. Could someone help...typing code echoes the lines later and the app freezes every now and then...HELP
Please sign in to leave a comment.
I have this problem too. The funny thing is that it seems to happen intermittently. Sometimes it's extremely fast even when editing very large files, and sometimes it's unbearingly slow. Restarting IDEA doesn't usually help, and sometimes it's really slow only a few minutes after starting IDEA, and simetimes I can run it for days without any problems.
I'm running Linux (Fedora Core 1).
I have a fast machine and it happens to me too.
It seems that the parser that runs in the background eats up all the power.
But to be honest, it only happens with files > 2000 Lines.
(very rarely the case in my projects, I try adapt my design in order to produce smaller classes)
I hate to mention this, because I hope the make IDEA perform well on all classess of any size...
... but most analyzers classify classes with > 300 lines GOD classes. 300 is a little low, but 3000 is a mother of a class. Realistically, can't you break it into smaller chunks?
Of course I would say that if you're running slow, refactoring it could be a handful.
I had similar problems when I switched to the 2.6 kernels. It seems that the latest eap releases of idea have been working without any more slowdowns. Not sure what it was. I'm currently using 2151.
Every time someone brings up performance problems with big classes someone tells them to break up the classes. And every time its the same reply - we don't own the code. Pretty much anyone who works on a large legacy app finds out that the people who came before them were, how shall i put this... technically challenged. And procedure keeps you from doing more then minimal changes for maintenance. So, we end up with monster classes and we complain about performance. And someone tells us to break them up and the cycle continues...
In article <4615192.1088639473160.JavaMail.email@example.com>,
Charles Wise <firstname.lastname@example.org> wrote:
Also, if you use a tool like Apache Axis to generate SOAP proxies for
small, data heavy classes, you can get some really huge classes to
manage the XML. All machine generated, and not something you should be