STS 3.0 (Really, Eclipse Juno) is slow...

Hi,
I have installed the Patch and also made the GC setting change in STS.ini,
but still not much improvements. Switching between the files is still taking bit time..
I also observed that switching between java and property files is bit quick but switching between XML files in editor does take long time..
Not sure if I am the only one who is getting this kind of behavior.

I am running 2 instances of STS and only the instance which is bit loaded (6 projects and approx 2000+ files) is having this problem.
The other instance works well for XML switching but it has very less load (less than 50 files).

Please note I am not opening these thousands of files in the Editor when I mentioned the switching.. But just normal 20-30 files at a time.

Sorry, I haven't performed any memory monitoring exercise.
Thanks.

Hey!

Can you capture a few thread dumps while it is taking a long time to switch something (using jps and jstack)? This is maybe not the best data to find performance issues, but maybe the easiest thing to do. Just find out the process ID of your running STS instance via jps and then do a jstack <processID> while STS is taking a long time. Maybe we can see something from that.

I usually work with STS while having something around 30-50 projects in the workspace (also with a lot of files), but I haven't experienced those issues yet, therefore my questions for more data... :-)

-Martin

Hi Martin,

I have just observed that, if I open XML files in a text or XML editor, the switching is very quick, like java and property files.
But if I open XML files in Spring Config Editor, then it takes bit time. I am using spring integration and I liked using Spring Config editor, since I can see integration-graph etc details. And I think this is taking a bit time since its generating graph and other GUI components, but in earlier version of STS (2.9.2), there was no delays using that editor.

May be this finding will help narrowing down the root cause?

Also, I have captured few thread dumps but not sure how to send these, as I am bit new to community.

I think, as of now I will keep using text/xml editor for working with XML files.

Thanks.

Just one more thing, its not only about switching between the files takes time, but even expanding different views (like Console, Problems, Servers etc) takes a while to expand. At least this was the behavior before the patch and after running STS for 2-3 hours.

Quote:

---

Originally Posted by nakulbhor

I have just observed that, if I open XML files in a text or XML editor, the switching is very quick, like java and property files.
But if I open XML files in Spring Config Editor, then it takes bit time. I am using spring integration and I liked using Spring Config editor, since I can see integration-graph etc details. And I think this is taking a bit time since its generating graph and other GUI components, but in earlier version of STS (2.9.2), there was no delays using that editor.

May be this finding will help narrowing down the root cause?

Also, I have captured few thread dumps but not sure how to send these, as I am bit new to community.

---

That is indeed a very interesting observation and will help narrow down this issue. Can you add this observation to this issue, together with your thread dumps:
https://issuetracker.springsource.com/browse/STS-2848

That would be great!

Quote:

---

Originally Posted by nakulbhor

Just one more thing, its not only about switching between the files takes time, but even expanding different views (like Console, Problems, Servers etc) takes a while to expand. At least this was the behavior before the patch and after running STS for 2-3 hours.

---

Did this change after you installed the patch?

Thanks for your help investigating these issues!!!
-Martin

Quote:

---

Originally Posted by nakulbhor

Hi Martin,

I have just observed that, if I open XML files in a text or XML editor, the switching is very quick, like java and property files.
But if I open XML files in Spring Config Editor, then it takes bit time. I am using spring integration and I liked using Spring Config editor, since I can see integration-graph etc details. And I think this is taking a bit time since its generating graph and other GUI components, but in earlier version of STS (2.9.2), there was no delays using that editor.

May be this finding will help narrowing down the root cause?

Also, I have captured few thread dumps but not sure how to send these, as I am bit new to community.

I think, as of now I will keep using text/xml editor for working with XML files.

Thanks.

---

I've filed a issue to run a profiler over the Spring Config Editor: https://issuetracker.springsource.com/browse/STS-2864

I've run Eclipse Memory Analysis Tools over the config editor in the past, and it has been very useful for tracking down resource leaks but I haven't run it lately. The config editor itself hasn't changed since 2.9.2, but if Eclipse or one of our dependent frameworks has changed something about the way resources are handled, then it could help to flag it down.

Hi Martin, I came back from vacation :)

Further I was investigated, this problem may be caused by eclipse bug.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=385272

The bug has been resolved, this problem might be resolved too.
In parallel, I'll try the solution you pointed(#15, #16).

Thanks a lot.

Hi,
I tried the patch(http://forum.springsource.org/showth...869#post422869), but this did not improve by my case..
So, I think the eclipse bug is main cause of this issue.

Thanks.

Hey!

Thanks for letting us know, we will keep a close eye on this.
In the meantime, you might want to switch to an Eclipse 3.8 Classic SDK and install STS and the other required parts manually, if you want. It is a bit work, but gives you the "old UI" feeling and hopefully the old performance in your case.

See, for example:
http://forum.springsource.org/showth...-Eclipse-3-8-0

HTH,
-Martin

Thanks for your help!

I changed an Eclipse 3.8 Classic SDK and installed STS 3.0, WTP, etc, it worked very well.
I did not know about Eclipse 3.8, and your advice was very helpful.

My issue is closed, and I wait that the eclipse bug is solved..
Thank you very much!