A few simple comparisons of Geronimo 2.2 and 2.1.5

[Kevan Miller <ke...@gmail.com>]

All,
I made a few (very simple) measurements comparing 2.2 to 2.1.5.  
Thought I'd pass them along.

As you can see, our server size has grown and EE server startup time  
is slower. I haven't looked at any specific causes. I don't view these  
as release show-stoppers. However, there may be some low-hanging  
fruit, that can be addressed quickly. Longer-term, I think it would be  
great to give these areas some focus. It would be interesting to  
measure memory footprint, also.

size   startup        artifact name
            time

  21M  1 second   geronimo-framework-2.1.5-SNAPSHOT-bin.tar.gz
  23M  1 second   geronimo-framework-2.2-SNAPSHOT-bin.tar.gz

  30M  3 seconds geronimo-jetty6-minimal-2.1.5-SNAPSHOT-bin.tar.gz
  34M  3 seconds geronimo-jetty7-minimal-2.2-SNAPSHOT-bin.tar.gz

  32M  4 seconds geronimo-tomcat6-minimal-2.1.5-SNAPSHOT-bin.tar.gz
  36M  4 seconds geronimo-tomcat6-minimal-2.2-SNAPSHOT-bin.tar.gz

  72M  12 seconds geronimo-jetty6-javaee5-2.1.5-SNAPSHOT-bin.tar.gz
  87M  17 seconds geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.tar.gz

  73M  11 seconds geronimo-tomcat6-javaee5-2.1.5-SNAPSHOT-bin.tar.gz
  88M  16 seconds geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.tar.gz

--kevan

Re: A few simple comparisons of Geronimo 2.2 and 2.1.5

[Ivan <xh...@gmail.com>]

In the past few days, I updated some console's pom files to add the provided
scope for some modules, so that those web applications will not keep some
duplicated jars in the lib folder.
I also found that in the activemq-ra, the default jms resource we defined in
our server copied some activemq related jars in its folder, please refer to
repository\org\apache\geronimo\configs\activemq-ra\2.2-SNAPSHOT\activemq-ra-2.2-SNAPSHOT.car\rar
in the binary build.
So, I wonder do we have any way to avoid this, or there is a reason that we
need to do this ?



2009/8/24 Kevan Miller <ke...@gmail.com>

> All,
> I made a few (very simple) measurements comparing 2.2 to 2.1.5. Thought I'd
> pass them along.
>
> As you can see, our server size has grown and EE server startup time is
> slower. I haven't looked at any specific causes. I don't view these as
> release show-stoppers. However, there may be some low-hanging fruit, that
> can be addressed quickly. Longer-term, I think it would be great to give
> these areas some focus. It would be interesting to measure memory footprint,
> also.
>
> size   startup        artifact name
>           time
>
>  21M  1 second   geronimo-framework-2.1.5-SNAPSHOT-bin.tar.gz
>  23M  1 second   geronimo-framework-2.2-SNAPSHOT-bin.tar.gz
>
>  30M  3 seconds geronimo-jetty6-minimal-2.1.5-SNAPSHOT-bin.tar.gz
>  34M  3 seconds geronimo-jetty7-minimal-2.2-SNAPSHOT-bin.tar.gz
>
>  32M  4 seconds geronimo-tomcat6-minimal-2.1.5-SNAPSHOT-bin.tar.gz
>  36M  4 seconds geronimo-tomcat6-minimal-2.2-SNAPSHOT-bin.tar.gz
>
>  72M  12 seconds geronimo-jetty6-javaee5-2.1.5-SNAPSHOT-bin.tar.gz
>  87M  17 seconds geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.tar.gz
>
>  73M  11 seconds geronimo-tomcat6-javaee5-2.1.5-SNAPSHOT-bin.tar.gz
>  88M  16 seconds geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.tar.gz
>
> --kevan
>



-- 
Ivan