Is there going to be some focus on performance for Diana, now that we're in the "final lap"?
I recently upgraded to a 4GB Windows XP machine, with a solid state hard disk, and Selena is now lightening quick. Diana on the other hand feels more and more painful, with each new release.
My current bug bears are:
- XML performance. I work on a lot of XML, XSL and XSD files and the performance around editing and reformatting seems to be getting worse rather than better. Editting any production-size files constantly canes the CPU and I've had to start reformatting in an evaluation version of XML Spy, as it just takes so long in IDEA. If the XML file content also happens to have no line breaks then IDEA just dies for minutes on end. I opened a file which was 1.5 million characters long on the first line, to reformat it to something readable, and hit the END key by accident - this caused the editor to just hang for minutes again. I know Maxim has been working on the performance around the reformatting, but anything which takes minutes to happen needs to have a progress bar at least!
- SQL performance. The one thing I was really looking forward to in Diana were the SQL inspections and syntax highlighting, but before it was removed (and even after), it was virtually impossible to even type in the editor when a 1000-line long SQL file was opened.
- Project startup/dialogs. Compared to Selena, Diana just seems incredibly memory hungry and additionally slow!
First time my main project is opened (indexing all files): 1m 10s
Normal time for project to open: 20s
Project config dialog change: 3s
First time my main project is opened (indexing all files): 2m 30s
Normal time for project to open: 30s
Project config dialog change (spends a lost of time "scanning files to index"): 10s
Diana won't even carry out the initial index of my project unless I give it 512MB of permgen - it just got stuck at 80% and hung. My major concern is that a majority of developers here are on slower laptop hard disks with only 1-2GB of RAM and my project opening times are usually 4-5x faster anyway - if those numbers are multiplied out for them, Diana is going to be painful! Additionally, allocating 512MB just for permgen space wouldn't even be an option for most of them.
I've raised a few JIRAs over the last few weeks for performance problems, but there's only so much time I can spend recording CPU snapshots while doing my job. Am I the only person who is seeing issues, as I've seen quite a few people recently praising the performance?