8 Replies Latest reply on Jun 9, 2009 8:18 PM by rkite01

    Memory footprint is more than twice as big from 4.2 to 5.1

      I don't have evergrowing vfs temp folders like i read about in other threads (this problem seems corrected in 5.1)
      Startup time is a bit longer but nothing terrible.

      BUT

      My application has about 150 EJBs and uses up (just after startup) about 400M on JBoss 4.2, but more than 800 on 5.1
      I know AS5 loads VFS info in memory but a double footprint is too much.
      It is not just the EJBs, without the ear the footprint is already more than 500m.

      Can i do anything about it? I want our project to migrate to AS5 but if i can't even launch 2 instances on my development machine, it will be hard to justify.

      My VM arguments:

      JAVA_OPTS="-Xms256m -Xmx512m -XX:MaxPermSize=256m -Xss128k -Xverify:none -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:-DisableExplicitGC -Dhibernate.cglib.use_reflection_optimizer=false -Djboss.platform.mbeanserver -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true"


        • 1. Re: Memory footprint is more than twice as big from 4.2 to 5
          jaikiran
          • 2. Re: Memory footprint is more than twice as big from 4.2 to 5

            Yes i had seen this JIRA while searching about this issue.

            But, is there any hope that it will be corrected in the near future? Should we wait for 5.2?
            I mean JBoss5 has been released for a while now and the JIRA says this problem was already here in 5.0 so i have a hard time imagining how you are going to reduce the memory usage by about half now (considering that even when i don't deploy anything it's already >500M).

            I'm a bit surprised it's just a JIRA somewhere, i mean a doubled footprint is a pretty huge issue right?

            Sorry for the impatient tone but i don't see how this is going to work for us or most projects in the current state.

            • 3. Re: Memory footprint is more than twice as big from 4.2 to 5
              jaikiran

               

              "chtimi2" wrote:

              i mean a doubled footprint is a pretty huge issue right?


              Yes, it is. There has been some work going on to bring down the performance issues, and there has been some steady progress. We still have some way to go to get all these performance issues resolved.

              My application has about 150 EJBs and uses up (just after startup) about 400M on JBoss 4.2, but more than 800 on 5.1

              As for this specific issue, without the EJBs being deployed, do you still see the issue?

              • 4. Re: Memory footprint is more than twice as big from 4.2 to 5

                Yes i'm at >500M without anything deployed with -c all and 460M with -c default.

                Do you mean that notwithstanding the "EJB footprint issue", i should be seeing a smaller memory footprint when deploying nothing? That amount seems to surprise you (when deploying nothing).

                If it was possible to reduce that "empty" usage to more reasonable levels it would be a lifesaver.

                My version is 5.1.0GA, on Ubuntu.

                • 5. Re: Memory footprint is more than twice as big from 4.2 to 5
                  jaikiran

                   

                  "chtimi2" wrote:

                  Do you mean that notwithstanding the "EJB footprint issue", i should be seeing a smaller memory footprint when deploying nothing? That amount seems to surprise you (when deploying nothing).

                  The reason i asked for the numbers without your EJB deployments was to ensure that the EJB deployments did not play a (major) role. And as expected it does not.

                  "chtimi2" wrote:

                  If it was possible to reduce that "empty" usage to more reasonable levels it would be a lifesaver.

                  Yes, that's the target.




                  • 6. Re: Memory footprint is more than twice as big from 4.2 to 5

                    So just to be sure i understand you, this "empty" footprint is a separate issue (from the deployment issue), that JBoss is also working on?

                    Is there any workaround for now or do we have to wait for 5.2?
                    Is JBoss 5 used in production and if so did the users just double their resources?

                    • 7. Re: Memory footprint is more than twice as big from 4.2 to 5
                      jaikiran

                       

                      "chtimi2" wrote:
                      So just to be sure i understand you, this "empty" footprint is a separate issue (from the deployment issue), that JBoss is also working on?

                      It's not a separate issue. It's one part of improving the performance of AS-5.x (the other part being improving the startup/deployment time).

                      "chtimi2" wrote:

                      Is there any workaround for now


                      AFAIK, there's no workaround yet. Please keep a watch on that JIRA or this forum. If there's some improvements in this area we will update the JIRA and this forum with the details.


                      • 8. Re: Memory footprint is more than twice as big from 4.2 to 5
                        rkite01

                        Doubling resources is not an option for us. We have about 1000 laptops at sites running JBoss as well as one large central site. The laptops have 4Gig of memory and core 2 Intel processors but other security software, Sybase Database and the OS take their fare share of memory as well. The max memory we can allow JBoss is 768Meg. It is amazing what little memory Windows allows applications to obtain.

                        Moving to JBoss 4.2.3 will stress our hardware to the max.