IDEA 94.426 - slow on properties file?

Seems to me that parsing/inspecting properties file is noticeably slower than that on Intellij8.  I'm using the latest EAP (94.426).  My project is a fairly straightforward Spring/Web application (no EJB) with about 220 java files.  I have a "message.properties" file with about 80 line of name/value pair.

I noticed that when I click on that properties file the first time after the project is opened (and indexing has completed), the hard drive light on my laptop went nuts for about 90+ seconds - Intellij became unresponsive during that time, mouse was very glitchy, and the memory indicator in Intellij shoot up from 120+M to 277M.

I don't suppose this slowness is specific to the latest build.  Seems to me that Intellij is "building" some sort of indexing between the keys in the "message.properties" file to the rest of the project -- which is very cool and useful I'm sure.  But if there's any way to speed this up, or span it over time, it'll definitely be very helpful.  Esp. since I have 5 more properties files for this project -- now I'm consciously avoiding to click on them...

I wonder if anyone else is experiencing the same thing as I.  I'm using XP SP2 on JDK 1.6._018-b07.  Here's my vmoptions:
-Dsun.awt.keepWorkingSetOnMinimize=true
-Xms256m
-Xmx512m
-XX:MaxPermSize=250m
-agentlib:yjpagent=disablej2ee,sessionname=IntelliJIdea90


Thank you.

mike

4 comments

I thought I would just add that editing this "message.properties" is also very slow.    The keyboard is slow to response and so is the mouse.

0

I have not experienced this. But in order for JetBrains to diagnose the problem, they'll need a CPU snapshot. See http://www.jetbrains.net/devnet/docs/DOC-192 for info on how to submit one.

0

Thanks for the suggestion.  I've done that.  Let's see what happens next.

0

For those that might have the same problem as I...

I sent in my CPU snapshot to IntelliJ support.  As it turned out, I had an inspection called "Unused Property" turned on -- perhaps by default at some point in time.  That was the culprit.  I turned it off and IntelliJ is back to its speedy self again!

Thanks to great people at IntelliJ support!

0

Please sign in to leave a comment.