Inspections runner takes extremely long to launch IDEA (>45min)
We want to use the Inspections Runner in TeamCity to run our IDEA Inspections. TeamCity takes over 45 minutes during the build to launch the integrated IDEA:
[10:28:39]Starting up IntelliJ IDEA 11.0.2 ...done.[11:13:18]Opening project...done.
Is this normal?
Do we have a misconfiguration?
The project is configured using the IDEA-Runner with .idea directory and .iml files.
Please sign in to leave a comment.
How large is your project? When IntelliJ IDEA starts it needs to index project files. If project is large enough it can take significant time.
It is a larger project with over 100 (hierarchical maven) modules. However, reindexing the project within IDEA only takes some minutes, not 45.
Does TeamCity cache the index for the next run?
Should we change to the "Maven-style" inspection runner to overcome the long indexing time?
Any other improvements possible?
In case of Maven I suppose some time can be spent on retrieving Maven dependencies. If this is reproducible please try to take thread dump from the build (see "View thread dump" link in the build) and attach it here.
Do you mean a thread dump of the idea-style indexing problem or the maven-style dependency problem?
The 45min to startup idea is reproducable. It always takes so long.
Just take several thread dumps from IDEA process, you should see process tree in the window opened when you click "View thread dump" link.
I created four ThreadDumps during the indexing process with a few minutes between each one.
Attachment(s):
thread-dump-tc-idea-04.txt.zip
thread-dump-tc-idea-03.txt.zip
thread-dump-tc-idea-02.txt.zip
thread-dump-tc-idea-01.txt.zip
Pavel, could you analyze the ThreadDumps? We would like to setup the Server-Side Inspections, but if the duration is so long, this is not possible.
As I didn't get any answer to the ThreadDumps, I created a YouTrack Issue:
http://youtrack.jetbrains.com/issue/TW-21985