Why is SpringSource Tool Suite (STS) so slow? And how can I fix it?

eclipse sts-springsourcetoolsuite spring-ide
curthipster picture curthipster · Apr 28, 2010 · Viewed 56k times · Source

I've been running STS 2.3.2 on a MacBook Pro for a few days now. I'm finding the performance to be significantly slower than any other build of Eclipse I've used. For example, switching from one tab to another can take up to 4 seconds.

I tried turning off much of the validation, and increasing the memory, but it's not making a difference.

Are others having similar experiences?

Answer

Michael Collins picture Michael Collins · Oct 1, 2010

I had the same problem on a MacBook Pro i7. Switching editors or views was painfully slow. Solved it by turning off Spring validators that I didn't need. Go to:

SpringSource Tool Suite -> Preferences -> Spring -> Project Validators

Specifically, I deselected all validators except for Spring Validator, Beans Validator and STS Bean Validator.

Related questions

Maven2: Missing artifact but jars are in place

From now to then, my Maven 2 started to mess around. I am using SPring STS 2.6.1 and have a single project based on Spring 3, Hibernate, DWR, Cometd and all that stuff. Today I just updated from Git und all of a …

Read More
SpringSource Tool Suite Change Themes

When I became aware of Sublime, I noticed the benefits of dark themes to your workspace. But since Sublime doesn't have support for Grails at the moment, I search for ways to theme STS or SpringSource Tool Suite and I …

Read More
Groovy/Grails - Unable to Resolve Class

I am trying to build a Grails project in STS and am getting many error messages of the form: Groovy:unable to resolve class org.codehaus.groovy.grails.commons.ConfigurationHolder as well as others like Groovy:unable to resolve class …

Read More