Performance problems with Eclipse/STS + Roo Project

[Christian Dupuis]

I am actually using the one that comes with the Mac installer for the Core Spring class. The latest Spring 3.0 class. I taught it two weeks ago and used the installer that is now on the pen drives.

Yeah, Core Spring 3.0 ships the Cocoa build which is known to have performance issues. Please try with a Carbon version.

Christian

[bytor99999]

Well, the Carbon version seems very slow too without modifying anything

Going to my apps page in STS

Start time
INFO: Initializing Spring FrameworkServlet 'bandapp'
2010-03-10 13:56:37

I guess deploy completion
2010-03-10 13:58:52,490 [tomcat-http--6] INFO org.springframework.web.servlet.DispatcherServlet - FrameworkServlet 'bandapp': initialization completed in 135026 ms

Now I changed the xms to 256M and kept the permgen at 256M and here are the faster results

INFO: Initializing Spring FrameworkServlet 'bandapp'
2010-03-10 14:35:53

2010-03-10 14:36:28,705 [tomcat-http--2] INFO org.springframework.web.servlet.DispatcherServlet - FrameworkServlet 'bandapp': initialization completed in 34909 ms

So from 2 minutes 15 seconds down to 35 seconds.

Just for anyone else who might have a slow STS running on Mac.

Mark

[Wolfram]

Also I found out that in my case most of the build time (and the afterwards occuring "validation" phase) is spend with getting the xsds for the spring (and spring security/ integration) xml files. It seems as if STS requests the xsds from the web instead of using the ones inside the according jar files.

@Wolfram Can you assure this isn't the case in your scenario?

Yes, that's not the case, never saw that action taking place in any log I checked. "Deleting and creating markers..." is where I am (or was? see below) stuck. A sidenote: "perform eclipse" does not add maven2Nature to my project, which is fine with me. I simply call that again when I add another dependency.

---

Right now, my problems come down to the recreation of all aspectj markers on every change. Normally I run into this by 1) changing something 2) saving the file 3) immediately see a typo or missing import, thus changing and saving again. This is when the nice window is popping up telling me that everyone including myself will have to wait for the markers.

However, I just finished installing STS 2.3.1 (carbon) and opened up a source file, tried the three steps above and no window is showing + the file is saved instantly. The markers are still recreated but the time needed dropped from 6s to 0.4s, which is nice. Let's hope it stays this way.

@Christian:
Looking forward to your talk in Munich ("Extreme Productivity with Spring Roo" ... and STS ?!). I'll closely keep an eye on the STS performance on stage (if you use it at all).