Performance in 7.0.2 and 7.0.3 EAP (7626) is awful

I have a fairly large project that uses Spring and Hibernate (JPA annotations). I am running on a Mac (Leopard), Core 2 Duo processor, and 4GB of RAM (1GB devoted solely to IDEA).

Performance in IDEA is almost unusable. Error highlighting and inspections are extremely slow (which greatly hurts productivity). I have to sit around for about 10 seconds waiting for IDEA to prompt me to import a class every time that I type a new class name. I regularly have to sit and wait on the editor to respond. I regularly don't see code problems until I go to compile because IDEA took so long to process the file that I didn't notice the errors.

I've submitted several JIRA issues with attached CPU snapshots, but this is ridiculous given the amount of resources available to IDEA. Are you guys testing with real-world size spring/hibernate projects?

I've heard that there will be performance improvements in the next 7.0.3 EAP. I sure hope so. Any idea when that will be released? I'm anxiously waiting...

27 comments

I'm having similar problems.

I have a quad core machine with 4GB of ram and pretty much anytime I open a
java file the entire IDE freezes for literally 4-5 seconds. It's terrible! I
even re-created my entire project (about 35+ modules) from scratch thinking
something got corrupted. It didn't change a thing.

I'm using the latest EAP as well. I have 5 java/jar spring/hibernate apps
and 20 web apps that include those spring/hibernate apps in addition to
referencing about 25 EJB client jar modules. I've resorted to using the
offline module plugin to disable half the plugins to get any reasonable
performance.



"Jeremy Haile" <no_reply@jetbrains.com> wrote in message
news:32386251.1200065145540.JavaMail.itn@is.intellij.net...
>I have a fairly large project that uses Spring and Hibernate (JPA
>annotations). I am running on a Mac (Leopard), Core 2 Duo processor, and
>4GB of RAM (1GB devoted solely to IDEA).
>

Performance in IDEA is almost unusable. Error highlighting and
inspections are extremely slow (which greatly hurts productivity). I have
to sit around for about 10 seconds waiting for IDEA to prompt me to import
a class every time that I type a new class name. I regularly have to sit
and wait on the editor to respond. I regularly don't see code problems
until I go to compile because IDEA took so long to process the file that I
didn't notice the errors.

>

I've submitted several JIRA issues with attached CPU snapshots, but this
is ridiculous given the amount of resources available to IDEA. Are you
guys testing with real-world size spring/hibernate projects?

>

I've heard that there will be performance improvements in the next 7.0.3
EAP. I sure hope so. Any idea when that will be released? I'm anxiously
waiting...


0

err I mean't disable half the modules not plugins.

I've tried tweaking the jvm params as well to give IDEA more ram but the
freezing isn't tied to garbage collection kicking off (I have plenty of ram
available). Literally it's when the IDE is analyzing a new java file to do
all of it's highlighting is when it freezes.

I'm almost thinking of switching back to IDEA 6.0 actually.




"Grant Gochnauer" <grant@gochnauer.org> wrote in message
news:fm83ae$2ta$1@is.intellij.net...

I'm having similar problems.

>

I have a quad core machine with 4GB of ram and pretty much anytime I open
a java file the entire IDE freezes for literally 4-5 seconds. It's
terrible! I even re-created my entire project (about 35+ modules) from
scratch thinking something got corrupted. It didn't change a thing.

>

I'm using the latest EAP as well. I have 5 java/jar spring/hibernate apps
and 20 web apps that include those spring/hibernate apps in addition to
referencing about 25 EJB client jar modules. I've resorted to using the
offline module plugin to disable half the plugins to get any reasonable
performance.

>
>
>

"Jeremy Haile" <no_reply@jetbrains.com> wrote in message
news:32386251.1200065145540.JavaMail.itn@is.intellij.net...

>>I have a fairly large project that uses Spring and Hibernate (JPA
>>annotations). I am running on a Mac (Leopard), Core 2 Duo processor, and
>>4GB of RAM (1GB devoted solely to IDEA).
>>
>> Performance in IDEA is almost unusable. Error highlighting and
>> inspections are extremely slow (which greatly hurts productivity). I
>> have to sit around for about 10 seconds waiting for IDEA to prompt me to
>> import a class every time that I type a new class name. I regularly have
>> to sit and wait on the editor to respond. I regularly don't see code
>> problems until I go to compile because IDEA took so long to process the
>> file that I didn't notice the errors.
>>
>> I've submitted several JIRA issues with attached CPU snapshots, but this
>> is ridiculous given the amount of resources available to IDEA. Are you
>> guys testing with real-world size spring/hibernate projects?
>>
>> I've heard that there will be performance improvements in the next 7.0.3
>> EAP. I sure hope so. Any idea when that will be released? I'm
>> anxiously waiting...


0

Please give your JIRA performance issue names.

0

Here is an issue I posted recently:
http://www.jetbrains.net/jira/browse/IDEADEV-24162

Here is another issue that I commented on and uploaded CPU snapshots: (this one was marked resolved for the latest EAP)
http://www.jetbrains.net/jira/browse/IDEADEV-23816

To Jetbrains credit, you are responding to these issues in a timely manner (either with a comment or resolution). However, I don't know that these two issues are comprehensive of the overall problem. I feel like the types of problems I am seeing would be very obvious if IDEA was being tested in these types of projects.

I have seen these issues since version 7 came out with spring/JPA/etc support.

To give more information about my project, we have a few hundred spring files with 2000+ bean definitions. (not all of which I have registered as config filesets due to the performance problems). We have about 300 JPA/Hibernate objects.

However, I can be browsing in a class that is completely unrelated to Spring or JPA and IDEA will still sometimes take 5-15 seconds for highlighting and inspections to update on the file and will be chewing up a good bit of CPU usage.

I have been using IDEA since version 3.0, so I'm anxiously awaiting the next EAP and hoping that it resolves some of these performance problems that makes the great new features (and using IDEA in general) almost impossible.

0

At least some things will be different in next 7.0.3 EAP. If it doesn't
help, please provide more snapshots.

0

http://www.jetbrains.net/jira/browse/IDEA-16867

Here is one I captured today. I had 8-10 second pause opening one java file.


"Peter Gromov (JetBrains)" <peter@jetbrains.com> wrote in message
news:fm8dnq$40s$1@is.intellij.net...

At least some things will be different in next 7.0.3 EAP. If it doesn't
help, please provide more snapshots.


0

Any estimate on when the next EAP might be made available? This week or next week?

0

How many DWR Spring beans do you have in your project? In fact, it's the
custom bean parsing that takes all the time (including setting up the
parsing environment). I see several solutions to this problem:

1. Disable this custom parsing at all. This may result in that those
bean name references will be red-highlighted (if there are any of them),
and those bean types will be undefined. If DWR XML Schema file has
Spring tooling annotations, everything should be OK and much quicker.

2. Maybe reduce your module classpath in some way, because IntelliJ IDEA
searches for namespace handlers there, and the more possibilities it
has, the longer time it takes. All it needs is in fact the DWR library
and Spring itself.

0

We're also using DWR and Spring by the way. We are using the @RemoteProxy and @RemoteMethod style DWR annotations. We do have a dwr.xml file to declare converters.

I haven't specifically enabled any DWR support, etc.

Our classpath is also pretty large (40-50 jars).

0

I have one DWR spring bean in about 3 modules and that is it.
 
I do have 3 custom name space parsers checked for 3 different modules.
 
The interesting thing is that I have these 3 spring/hibernate/dwr modules defined however then I have 7 or 8 other web apps that use those modules. In those 7 or 8 web apps, I have in the spring facet all of the xmls from the included modules attached to that facet + all the other spring beans in that particular web app. In each web app and java spring module I have the customer namespaces being validated.
 
It's interesting that the JMS and context schemas are considered custom when they come right out of the normal spring distro.
 
 
 
"Peter Gromov (JetBrains)" <peter@jetbrains.com> wrote in message news:fm8fgj$301$1@is.intellij.net...
> How many DWR Spring beans do you have in your project? In fact, it's the
> custom bean parsing that takes all the time (including setting up the
> parsing environment). I see several solutions to this problem:
>
> 1. Disable this custom parsing at all. This may result in that those
> bean name references will be red-highlighted (if there are any of them),
> and those bean types will be undefined. If DWR XML Schema file has
> Spring tooling annotations, everything should be OK and much quicker.
>
> 2. Maybe reduce your module classpath in some way, because IntelliJ IDEA
> searches for namespace handlers there, and the more possibilities it
> has, the longer time it takes. All it needs is in fact the DWR library
> and Spring itself. ]]>



Attachment(s):
Capture.JPG
0

Our classpath is also very large. I'm included our WAS 5.1 lib folder as a
base project library which is about 80 jars alone and it's attached to every
module.


"Jeremy Haile" <no_reply@jetbrains.com> wrote in message
news:23326565.1200079864501.JavaMail.itn@is.intellij.net...

We're also using DWR and Spring by the way. We are using the @RemoteProxy
and @RemoteMethod style DWR annotations. We do have a dwr.xml file to
declare converters.

>

I haven't specifically enabled any DWR support, etc.

>

Our classpath is also pretty large (40-50 jars).


0

Do DWR beans have relationships with plain Spring beans, are they
referenced from anywhere? If not, it's safe to disable DWR parsing in
Spring facet configuration. You may have enabled it without noticing,
it's pretty simple, just Alt+Enter.

0

They do have relationships with normal spring beans. I'm using the "spring
way" of configuring DWR in my application. So for example, I have an
applicationContext-dwr.xml file that contains:

]]>
-



Now that I disabled the custom DWR parser, my <dwr:configuration> element is
highlighted since it isn't recognized but at least it's just a warning and
not an error.


"Peter Gromov (JetBrains)" <peter@jetbrains.com> wrote in message
news:fmf970$cp1$1@is.intellij.net...

Do DWR beans have relationships with plain Spring beans, are they
referenced from anywhere? If not, it's safe to disable DWR parsing in
Spring facet configuration. You may have enabled it without noticing, it's
pretty simple, just Alt+Enter.


0

Performance in 7648 is equally as bad as 7626 with my project. Editing most any file seems to be really slow. I waited two minutes for one of my Hibernate DAO classes to highlight, and finally gave up. During those two minutes, IDEA will not indicate errors correctly or prompt me to import classes. That is unusable in a professional environment!!

I've updated my JIRA issue regarding performance issues with two new snapshots from 7648:
http://www.jetbrains.net/jira/browse/IDEADEV-24162

Two of my co-workers are also trying to use IDEA, and find it painfully slow (both with dual cores and 2-4 gigs of RAM). One of them mentioned that editing JSPs with 7648 seems even slower than 7626. Two other co-workers refuse to switch to IDEA from Eclipse due to the performance being terrible. I realize that my company switching away from IDEA is not a real incentive for you guys to prioritize this, but I can't be the only person out there experiencing these performance issues. I don't think our project is anything out of the ordinary (although perhaps larger than average and using JDK 5 features, annotations, and Spring/Hibernate facets).

0

Is the performance better now?

0

Just to confirm - I too find the performance awful on a Spring/maven project with the Spring Facet enabled (on a project which has about 400 spring bean definitions’ in around 55 application context files whit at least a third of the 55 being auto detected and picked up from within maven jar dependencies – local repo).

Temporary workaround:
In the spring facet – I delete the MVC application context (auto detected) node
This makes everything much smoother (as I said this is just a workaround)

It actually looks like (in the spring facet) deleting MVC application context references which points inside jar files (ref temporary workaround) will speed things up. (Could it a problem indexing inside many jar’s?)

-Bjørn

0

Could you provide a CPU snapshots with and without MVC?

0

Uploaded ‘7648_SPRING_CPU_SNAPSHOTS.zip’

0

Uploaded ‘7648_SPRING_CPU_SNAPSHOTS.zip’

Thank you very much! Check the upcoming EAP.

0

Check the upcoming EAP, performance should be better now

0

Excellent! I can't wait!

I saw Maxim also fixed my big JSP parser issue so I am definitely excited
for next EAP build!
http://www.jetbrains.net/jira/browse/IDEADEV-24318


"Peter Gromov (JetBrains)" <peter@jetbrains.com> wrote in message
news:fmo8dn$t6j$2@is.intellij.net...

Check the upcoming EAP, performance should be better now


0

Have you guys made any performance improvements that would affect JSP editing since 7648?

I receive constant lockups while editing JSP. While editing JSPs, IDEA will freeze up and be unresponsive for a few seconds quite regularly. Even when doing things like scrolling down the file.

Any idea when the next EAP will be released? I am literally refreshing the EAP download page every hour hoping for a build of IDEA that is usable from a performance perspective. (with 1GB of dedicated RAM on a dual core processor...which you wouldn't think would be a problem)

0

I uploaded a CPU snapshot during some JSP slowdowns. Almost anytime I scroll the editor window up and down in a JSP, it lags and freezes.

http://www.jetbrains.net/jira/browse/IDEA-16906

0

Any idea when the next EAP will be released?

Most probably in a few hours

0

Environment:
Hard:
Intel Dual Core Exteme
4GB RAM
120BG HD

Soft:
JDK 1.6.0_07
IntelliJ 7.0.3 build #7757 ( I have some type of enterprise license )
Ubuntu 7.04 Fiesty Fawn

IntelliJ Project: medium - large - Spring / Hibernate / Tiles

Problem:
JSP editor is unusably slow. I've tried several different JDK 1.6 versions, and I found that 1.6.0_06 is the worst JDK to use. IntelliJ will freeze for 30seconds to a minute before "coming back" to a usable state. During the "freeze" state, CPU usage for IntelliJ thread would hover around 70%-99% before "coming back" to a usable state, and the memory usage is at normal levels at all times. No exceptions are thrown in my intelliJ terminal.

I also found that my other projects that don't use JSTL or Tiles render much quicker in the jsp editor.

I'm convinced that intelliJ is having a problem trying to resolve tile definitions and jsps with large amounts of JSTL and tiles imports in it.

Please post if anyone has confirmed my suspicion.

Edited by: James H. on Jul 16, 2008 4:47 AM

Edited by: James H. on Jul 16, 2008 4:49 AM

Edited by: James H. on Jul 16, 2008 5:08 AM

0

Hello James H.,

There is no need to try out different JDK versions or guess about reasons
for slow performance, because IntelliJ IDEA provides tools for diagnosing
performance problems very specifically. Please take a CPU snapshot as described
in:
http://support.jetbrains.com/kb/entry.jspa?externalID=192&categoryID=5
then create a JIRA issue at http://www.jetbrains.net/jira and attach the
snapshot to it.

Environment:
JDK 1.6.0_07
IntelliJ 7.0.3 build #7757 ( I have some type of enterprise license )
Ubuntu 7.04 Fiesty Fawn
IntelliJ Project: medium - large - Spring / Hibernate / Tiles

Problem:
JSP editor is unusably slow. I've tried several different JDK 1.6
versions, and I found that 1.6.0_06 is the worst JDK to use.
I also found that my other projects that don't use JSTL or Tiles
render much quicker in the jsp editor.

I'm convinced that intelliJ is having a problem trying to resolve tile
definitions and jsps with large amounts of JSTL and tiles imports in
it.

Please post if anyone has confirmed my suspicion.

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

Dima, thanks for your reply. Your link lead me to my problem, which resulted in 10's of thousands of unversioned files.

Everything is snappy now. Thank you.

0

Please sign in to leave a comment.