Details

    • Type: Sub-task Sub-task
    • Status: Open Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.1.0.RELEASE
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Windows, Java 1.7.0_09 (32 bit) with JRebel.

      Description

      STS seems to use a lot of memory. The memory footprint for STS 3.1 (built on the old Eclipse 3.8 platform) relative to plain Eclipse Java EE is:

      STS 3.1: 594MB
      Eclipse 3.7 for Java EE, plus m2e plugin: 380MB

      Telemetry shows that most of this memory is in fact free heap, meaning there are high peaks. For example, jconsole currently shows me 129MB used out of total 380MB heap. I will attach a HPROF heap dump to this issue.

      1. sts-3.2.0-STS-3040.jps
        3.22 MB
        Christopher Wong
      2. xaa
        10.00 MB
        Christopher Wong
      3. xab
        10.00 MB
        Christopher Wong
      4. xac
        10.00 MB
        Christopher Wong
      5. xad
        10.00 MB
        Christopher Wong
      6. xae
        10.00 MB
        Christopher Wong
      7. xaf
        7.29 MB
        Christopher Wong

        Activity

        Hide
        Martin Lippert (c) added a comment -

        Thank you very much for the nice feedback. Much appreciated!!!

        Show
        Martin Lippert (c) added a comment - Thank you very much for the nice feedback. Much appreciated!!!
        Hide
        Martin Lippert (c) added a comment -

        Hey Christopher! I worked on a reduced memory consumption again and made some improvements in the latest builds of STS. We have now an STS 3.3.0.RC1 build available and it would be great if you could give it a try. Maybe you can compare your previous profiles with this newer version to see if this improves things in your environment as well? And attaching a memory profiling with recorded allocation points would also be great, if you can spend the time. Would help me a lot to do further improvements.
        You can download the RC1 build here (guessing you would like to use the Windows 32bit or 64bit versions):
        http://dist.springsource.com/milestone/STS/3.3.0.RC1/dist/e3.8/spring-tool-suite-3.3.0.RC1-e3.8.2-win32.zip
        http://dist.springsource.com/milestone/STS/3.3.0.RC1/dist/e3.8/spring-tool-suite-3.3.0.RC1-e3.8.2-win32-x86_64.zip

        If you need other versions (like the one on Eclipse 4.3, for example, let me know).
        Thanks a lot for your help in advance!!!

        Show
        Martin Lippert (c) added a comment - Hey Christopher! I worked on a reduced memory consumption again and made some improvements in the latest builds of STS. We have now an STS 3.3.0.RC1 build available and it would be great if you could give it a try. Maybe you can compare your previous profiles with this newer version to see if this improves things in your environment as well? And attaching a memory profiling with recorded allocation points would also be great, if you can spend the time. Would help me a lot to do further improvements. You can download the RC1 build here (guessing you would like to use the Windows 32bit or 64bit versions): http://dist.springsource.com/milestone/STS/3.3.0.RC1/dist/e3.8/spring-tool-suite-3.3.0.RC1-e3.8.2-win32.zip http://dist.springsource.com/milestone/STS/3.3.0.RC1/dist/e3.8/spring-tool-suite-3.3.0.RC1-e3.8.2-win32-x86_64.zip If you need other versions (like the one on Eclipse 4.3, for example, let me know). Thanks a lot for your help in advance!!!
        Hide
        Martin Lippert (c) added a comment -

        Hey Christopher! Any chance to take a look at the RC1 bits?

        Show
        Martin Lippert (c) added a comment - Hey Christopher! Any chance to take a look at the RC1 bits?
        Hide
        Christopher Wong added a comment -

        Hi Martin. Unfortunately, I recently changed jobs and now have no access to the original project nor JProfiler. I tried to use the free jvisualvm profiler on my current project, but it was unusable in that mode, and the new project (Spring/Gradle, not Spring/Maven) is not comparable anyway. Since I am no longer in a position to verify this work, I suggest you resolve this issue. If I'm in a position to profile STS again I'll open an new issue.

        Thanks for working on performance/memory issues. I appreciate the fact that this project takes these issues seriously.

        Show
        Christopher Wong added a comment - Hi Martin. Unfortunately, I recently changed jobs and now have no access to the original project nor JProfiler. I tried to use the free jvisualvm profiler on my current project, but it was unusable in that mode, and the new project (Spring/Gradle, not Spring/Maven) is not comparable anyway. Since I am no longer in a position to verify this work, I suggest you resolve this issue. If I'm in a position to profile STS again I'll open an new issue. Thanks for working on performance/memory issues. I appreciate the fact that this project takes these issues seriously.
        Hide
        Martin Lippert (c) added a comment -

        Hey Christopher! Thanks for letting us know. No problem at all and thanks again for all the good data and feedback around this issue. I think the 3.3.0 release will have an improved memory-related behavior, but there is still work to do. So we will continue to work in this area even after the 3.3.0 release.

        Show
        Martin Lippert (c) added a comment - Hey Christopher! Thanks for letting us know. No problem at all and thanks again for all the good data and feedback around this issue. I think the 3.3.0 release will have an improved memory-related behavior, but there is still work to do. So we will continue to work in this area even after the 3.3.0 release.

          People

          • Assignee:
            Martin Lippert (c)
            Reporter:
            Christopher Wong
          • Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              First Response Date: