2 Replies Latest reply on Jul 19, 2007 1:10 PM by adrian.brock

    AS Startup time suggestions?

    bytor99999 Jul 19, 2007 12:36 PM

      So is there any suggestions for how to cut down startup time here? I mean anything I can do on my "install" that would speed it up.

      Thanks

      09:24:58,500 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding
,name=JmsXA' to JNDI name 'java:JmsXA'
09:24:58,593 INFO [RARDeployment] Required license terms exist, view vfsfile:/C:/JBossSVN/jboss-head/build/output/jboss
-5.0.0.Beta3/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
09:28:21,062 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
09:28:21,078 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
09:28:21,078 INFO [RAMJobStore] RAMJobStore initialized.


      • 11835 Views
      • Tags:
        • 1. Re: AS Startup time suggestions?
          adrian.brock Jul 19, 2007 1:07 PM (in response to bytor99999)

          THIS IS NOT A DEVELOPMENT TOPIC.

          I don't care if you work for JBoss/Redhat, help requests go in the user forums.

          If you want to run a profiler and give some feedback on where it is spending
          its time then that would be a development topic.

          My simple look at this problem (taking random thread dumps
          to see what the deployment thread was doing)
          caught it spending most of the time analysing AOP pointcut bindings.

          I've made no quantative effort on this subject and I personally am
          not going to look at optimization until we get closer to the final release.
          "Early optimization is the root of all evil". :-)

            • Actions
          • 2. Re: AS Startup time suggestions?
            adrian.brock Jul 19, 2007 1:10 PM (in response to bytor99999)

             

            "adrian@jboss.org" wrote:

            I've made no quantative effort on this subject and I personally am
            not going to look at optimization until we get closer to the final release.
            "Early optimization is the root of all evil". :-)


            And even then the main optimization effort should be spent on the runtime
            not the deployment.

            It's perfectly acceptable to slow down the bootstrap to improve runtime performance.
            e.g. the classloader creates an index of every package in every jar deployed to speed up
            the classloading during the runtime.

              • Actions