9 Replies Latest reply on Aug 30, 2008 2:50 PM by Chris Simons

    Performance issues getting severe

    Chris Simons Expert


      Hi JBoss Tools Team,

      I don't want to say this is strictly a JBoss Tools issue given that Eclipse certainly won't be winning awards any awards under the "Performance" category.

      However, I'd like to point out some concerns myself and our team is having regarding the performance of our workspace.

      After prolonged usage (generally 6+ hours), our Eclipse processes are nearing 1 GB in memory usage. Opening JSF pages becomes a 2-3 minute process with Eclipse becoming unresponsive until the time it has let go of the resources it is using to open the page. We are setting the default view to "Source" but it seems to still try and load some of the visual components, as evidenced by some of the log messages I receive. Our JSF pages generally include several ui:includes to facelets and we are using Seam.

      When the memory usage hovers just below 1 GB, we commonly receive "out of memory" messages and we are asked if we want to shutdown. At this point, we close and restart Eclipse. Memory usage at this point is now at about 200 MB. At this point, memory usage jumps by about 30 MB per JSF page that we open and rarely do I see this memory being returned back to the system after the JSF pages are closed.

      Anyways, this is really becoming a drag. Is there anything we can do to improve overall performance and response times?

      Some of the things we have done to try and improve performance:
      * Turning all Seam Validator settings to "Ignore"
      * Setting default JSF view to "Source"


      Below are our specs and version numbers:

      Eclipse
      Version: 3.3.1.1
      Build id: M20071023-1652

      JBoss Tools
      2.0.0.GA

      Seam
      2.0 GA

      JSF 1.2; RichFaces 3.2.1

      System
      Lenovo T61; Dual Core 2.5 Ghz
      2 GB RAM
      160 GB HDD
      (i.e. the system should not be a problem, this is a fast machine)

      Some workspace/project specs:
      * We keep only one project open at at time
      * Project usually has roughly 100 JSF pages
      * Project usually has roughly 50 session beans accompanied by 30 entity beans