You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by Dok Sander <do...@yahoo.com> on 2012/06/24 14:04:10 UTC
Performance between 2.2.1 & 3.0.0
Hello,
This was discussed with kevan to some extend on geronimo IRC channel on Freenode.
There seems to be a considerable performance hit between Geronimo 2.2.1 and 3.0.0. In addition to results below the overall loading times of the web UI are much longer in 3.0.0 than in 2.2.1. I understand this is a good time to try and find if the performance can be made better since the actual release of 3.0.0 is drawing near.
-- vdox
Platform specs:
# uname -s -r -v -m -p -i -o
Linux 3.1.10-1.9-ec2 #1 SMP Thu Apr 5 18:48:38 UTC 2012 (4a97ec8) x86_64 x86_64 x86_64 GNU/Linux
# free -t
total used free shared buffers cached
Mem: 1751644 1385060 366584 0 64644 827940
-/+ buffers/cache: 492476 1259168
Swap: 0 0 0
Total: 1751644 1385060 366584
# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 26
model name : Intel(R) Xeon(R) CPU E5507 @ 2.27GHz
stepping : 5
cpu MHz : 2266.746
cache size : 4096 KB
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu de tsc msr pae cx8 apic sep cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc up rep_good nopl nonstop_tsc aperfmperf pni ssse3 cx16 sse4_1 sse4_2 popcnt hypervisor lahf_lm dts
bogomips : 4555.21
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
# java -version
java version "1.7.0_b147-icedtea"
OpenJDK Runtime Environment (suse-1.2-x86_64)
OpenJDK 64-Bit Server VM (build 22.0-b10, mixed mode)
-------------
Test results:
Following JAVA_OPTS are used for both versions:
-Xmx512m -Xms256m -XX:MaxPermSize=256m
geronimo-tomcat6-javaee5-2.2.1
___________________________________________________________________________________________________________________________
startup(From geronimo.out):
Startup completed in 1:46.803s seconds
list modules
# time /$GERONIMO_HOME/bin/deploy.sh -u system -p manager list-modules
...
real 0m13.703s
user 0m9.617s
sys 0m0.648s
deploy
# time $GERONIMO_HOME/bin/deploy.sh -u system -p manager deploy --inPlace
...
real 0m12.815s
user 0m9.137s
sys 0m0.740s
undeploy:
# time $GERONIMO_HOME/bin/deploy.sh -u system -p manager undeploy org.apache.geronimo.samples/HelloWorldApp/1.0/war
...
real 0m13.562s
user 0m10.457s
sys 0m0.840s
CPU usage during deploy list-modules:
geronimo: 0-20%
deploy: 50-90%
___________________________________________________________________________________________________________________________
geronimo-tomcat7-javaee6-3.0.03.0.0-20120620.212946 (I originally tested with 3.0.0-beta1 but snapshot was recommended to me by kevan)
___________________________________________________________________________________________________________________________
startup(From geronimo.out):
"Startup completed in 2:20.080s seconds"
list modules:
time $GERONIMO_HOME/bin/deploy -u system -p manager list-modules
...
real 0m51.848s
user 0m36.230s
sys 0m3.376s
deploy:
time $GERONIMO_HOME/bin/deploy -u system -p manager deploy --inPlace .
...
real 0m56.284s
user 0m32.822s
sys 0m3.680s
undeploy:
time $GERONIMO_HOME/bin/deploy -u system -p manager undeploy org.apache.geronimo.samples/HelloWorldApp/1.0/war
...
real 0m47.336s
user 0m32.862s
sys 0m2.764s
CPU usage during deploy list-modules:
geronimo: 80-90%
deploy: 10-20%
___________________________________________________________________________________________________________________________
Re: Performance between 2.2.1 & 3.0.0
Posted by xanadu72 <su...@gmail.com>.
I tried to disable several components i didn't use. You can gain several
seconds at boot time by disabling some modules :
Apache Wink
Apache Aries
UDDI
Active MQ
etc...
You can disable Felix if you are using the default Equinox framework
More details at :
http://www.java-tutorial.ch/apache-geronimo/optimize-geronimo-30 Optimize
Geronimo 3.0
--
View this message in context: http://apache-geronimo.328035.n3.nabble.com/Performance-between-2-2-1-3-0-0-tp3985246p3985278.html
Sent from the Users mailing list archive at Nabble.com.
Fw: Performance between 2.2.1 & 3.0.0
Posted by Dok Sander <do...@yahoo.com>.
----- Forwarded Message -----
From: Dok Sander <do...@yahoo.com>
To: Forrest Xia <fo...@gmail.com>; "user@geronimo.apache.org" <us...@geronimo.apache.org>
Sent: Monday, June 25, 2012 4:59 PM
Subject: Re: Performance between 2.2.1 & 3.0.0
Hi!
Yes, I don't really see the startup time as an issue(Since it wasn't
drastically longer between the versions, IMO) but the operation time of
the deploy command/module and overall portlet latency should be shorter. I could add my findings to the issue 6222.
--vdox
________________________________
From: Forrest Xia <fo...@gmail.com>
To: user@geronimo.apache.org; Dok Sander <do...@yahoo.com>
Sent: Monday, June 25, 2012 7:01 AM
Subject: Re: Performance between 2.2.1 & 3.0.0
Hi vdox,
Thank you for your testing on server startup and deployment time performance. I think they are useful information for the community to trigger some analysis. But before that, I also did some testing on my linux box(Ubuntu 10.04 x86_64). Here are my configuration and results:
$ uname -a
Linux forrestxm-u64 2.6.32-41-generic #90-Ubuntu SMP Tue May 22 11:29:51 UTC 2012 x86_64 GNU/Linux
$ free -t
total used free shared buffers cached
Mem: 3608260 2856884 751376 0 1196196 735504
-/+ buffers/cache: 925184 2683076
Swap: 4305912 40024 4265888
Total: 7914172 2896908 5017264
$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz
stepping : 8
cpu MHz : 2601.000
cache size : 3072 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 1
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss syscall nx lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni ds_cpl ssse3 cx16 popcnt lahf_lm ida arat
bogomips : 5202.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz
stepping : 8
cpu MHz : 2601.000
cache size : 3072 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 1
apicid : 3
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss syscall nx lm constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable nonstop_tsc aperfmperf pni ds_cpl ssse3 cx16 popcnt lahf_lm ida arat
bogomips : 5202.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
$ java -version
java version "1.6.0_29"
Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02, mixed mode)
$ export GERONIMO_OPTS="-Djava.security.egd=file:/dev/./urandom"
G 2.2.1
1. First time startup: Startup completed in 16.641s seconds
2. Second time startup: Startup completed in 14.357s seconds
G 3.0.0-SNAPSHOT built on 20120620:
1. First time startup: Startup completed in 21.995s seconds
2. Second time startup: Startup completed in 15.935s seconds
So from the startup time results of mine, there is no big gap between 2.2.1 and 3.0.0-SNAPSHOT. But, for deployment time, there are some gaps saw from my results as well.
About the deployment time issue, there is a known jira opened (https://issues.apache.org/jira/browse/GERONIMO-6222), also there are some improvements implemented in https://issues.apache.org/jira/browse/GERONIMO-5813.
On Sun, Jun 24, 2012 at 8:04 PM, Dok Sander <do...@yahoo.com> wrote:
Hello,
>
> This was discussed with kevan to some extend on geronimo IRC channel on Freenode.
>
>There seems to be a considerable performance hit between Geronimo 2.2.1 and 3.0.0. In addition to results below the overall loading times of the web UI are much longer in 3.0.0 than in 2.2.1. I understand this is a good time to try and find if the performance can be made better since the actual release of 3.0.0 is drawing near.
>
>
>
>-- vdox
>
>
>
>Platform specs:
>
># uname -s -r -v -m -p -i -o
>Linux 3.1.10-1.9-ec2 #1 SMP Thu Apr 5 18:48:38 UTC 2012 (4a97ec8) x86_64 x86_64 x86_64 GNU/Linux
>
># free -t
> total used free shared buffers cached
>Mem: 1751644 1385060 366584 0 64644 827940
>-/+ buffers/cache: 492476 1259168
>Swap: 0 0 0
>Total: 1751644 1385060 366584
>
># cat /proc/cpuinfo
>processor : 0
>vendor_id : GenuineIntel
>cpu family : 6
>model : 26
>model name : Intel(R) Xeon(R) CPU E5507 @ 2.27GHz
>stepping : 5
>cpu MHz : 2266.746
>cache size : 4096 KB
>fpu : yes
>fpu_exception : yes
>cpuid level : 11
>wp : yes
>flags : fpu de tsc msr pae cx8 apic sep cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc up rep_good nopl nonstop_tsc aperfmperf pni ssse3 cx16 sse4_1 sse4_2 popcnt hypervisor lahf_lm dts
>bogomips : 4555.21
>clflush size : 64
>cache_alignment : 64
>address sizes : 40 bits physical, 48 bits virtual
>power management:
>
># java -version
>java version "1.7.0_b147-icedtea"
>OpenJDK Runtime Environment (suse-1.2-x86_64)
>OpenJDK 64-Bit Server VM (build 22.0-b10, mixed mode)
>
>
>-------------
>
>Test results:
>
>
>Following JAVA_OPTS are used for both versions:
>-Xmx512m -Xms256m -XX:MaxPermSize=256m
>
>
>
>geronimo-tomcat6-javaee5-2.2.1
>___________________________________________________________________________________________________________________________
>
>
>startup(From geronimo.out):
>Startup completed in 1:46.803s seconds
>
>list modules
># time /$GERONIMO_HOME/bin/deploy.sh -u system -p manager list-modules
>...
>real 0m13.703s
>user 0m9.617s
>sys 0m0.648s
>
>
>deploy
># time $GERONIMO_HOME/bin/deploy.sh -u system -p manager deploy --inPlace
>...
>real 0m12.815s
>user 0m9.137s
>sys 0m0.740s
>
>undeploy:
># time $GERONIMO_HOME/bin/deploy.sh -u system -p manager undeploy org.apache.geronimo.samples/HelloWorldApp/1.0/war
>...
>real 0m13.562s
>user 0m10.457s
>sys 0m0.840s
>
>
>CPU usage during deploy list-modules:
>geronimo: 0-20%
>deploy: 50-90%
>___________________________________________________________________________________________________________________________
>
>
>
>
>
>geronimo-tomcat7-javaee6-3.0.03.0.0-20120620.212946 (I originally tested with 3.0.0-beta1 but snapshot was recommended to me by kevan)
>___________________________________________________________________________________________________________________________
>
>startup(From geronimo.out):
>"Startup completed in 2:20.080s seconds"
>
>
>list modules:
>time $GERONIMO_HOME/bin/deploy -u system -p manager list-modules
>...
>real 0m51.848s
>user 0m36.230s
>sys 0m3.376s
>
>
>deploy:
>time $GERONIMO_HOME/bin/deploy -u system -p manager deploy --inPlace .
>...
>real 0m56.284s
>user 0m32.822s
>sys 0m3.680s
>
>
>undeploy:
>time $GERONIMO_HOME/bin/deploy -u system -p manager undeploy org.apache.geronimo.samples/HelloWorldApp/1.0/war
>...
>real 0m47.336s
>user 0m32.862s
>sys 0m2.764s
>
>
>
>CPU usage during deploy list-modules:
>geronimo: 80-90%
>deploy: 10-20%
>
>___________________________________________________________________________________________________________________________
>
--
Thanks!
Regards, Forrest
Re: Performance between 2.2.1 & 3.0.0
Posted by Forrest Xia <fo...@gmail.com>.
Hi vdox,
Thank you for your testing on server startup and deployment time
performance. I think they are useful information for the community to
trigger some analysis. But before that, I also did some testing on my linux
box(Ubuntu 10.04 x86_64). Here are my configuration and results:
$ uname -a
Linux forrestxm-u64 2.6.32-41-generic #90-Ubuntu SMP Tue May 22 11:29:51
UTC 2012 x86_64 GNU/Linux
$ free -t
total used free shared buffers cached
Mem: 3608260 2856884 751376 0 1196196 735504
-/+ buffers/cache: 925184 2683076
Swap: 4305912 40024 4265888
Total: 7914172 2896908 5017264
$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz
stepping : 8
cpu MHz : 2601.000
cache size : 3072 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 1
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss syscall nx lm
constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable
nonstop_tsc aperfmperf pni ds_cpl ssse3 cx16 popcnt lahf_lm ida arat
bogomips : 5202.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz
stepping : 8
cpu MHz : 2601.000
cache size : 3072 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 1
apicid : 3
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss syscall nx lm
constant_tsc arch_perfmon pebs bts rep_good xtopology tsc_reliable
nonstop_tsc aperfmperf pni ds_cpl ssse3 cx16 popcnt lahf_lm ida arat
bogomips : 5202.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
$ java -version
java version "1.6.0_29"
Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02, mixed mode)
$ export GERONIMO_OPTS="-Djava.security.egd=file:/dev/./urandom"
G 2.2.1
1. First time startup: Startup completed in 16.641s seconds
2. Second time startup: Startup completed in 14.357s seconds
G 3.0.0-SNAPSHOT built on 20120620:
1. First time startup: Startup completed in 21.995s seconds
2. Second time startup: Startup completed in 15.935s seconds
So from the startup time results of mine, there is no big gap between 2.2.1
and 3.0.0-SNAPSHOT. But, for deployment time, there are some gaps saw from
my results as well.
About the deployment time issue, there is a known jira opened (
https://issues.apache.org/jira/browse/GERONIMO-6222), also there are some
improvements implemented in
https://issues.apache.org/jira/browse/GERONIMO-5813.
On Sun, Jun 24, 2012 at 8:04 PM, Dok Sander <do...@yahoo.com> wrote:
> Hello,
>
> This was discussed with kevan to some extend on geronimo IRC channel on
> Freenode.
>
> There seems to be a considerable performance hit between Geronimo 2.2.1
> and 3.0.0. In addition to results below the overall loading times of the
> web UI are much longer in 3.0.0 than in 2.2.1. I understand this is a good
> time to try and find if the performance can be made better since the actual
> release of 3.0.0 is drawing near.
>
>
>
> -- vdox
>
>
>
> Platform specs:
>
> # uname -s -r -v -m -p -i -o
> Linux 3.1.10-1.9-ec2 #1 SMP Thu Apr 5 18:48:38 UTC 2012 (4a97ec8) x86_64
> x86_64 x86_64 GNU/Linux
>
> # free -t
> total used free shared buffers cached
> Mem: 1751644 1385060 366584 0 64644 827940
> -/+ buffers/cache: 492476 1259168
> Swap: 0 0 0
> Total: 1751644 1385060 366584
>
> # cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 26
> model name : Intel(R) Xeon(R) CPU E5507 @ 2.27GHz
> stepping : 5
> cpu MHz : 2266.746
> cache size : 4096 KB
> fpu : yes
> fpu_exception : yes
> cpuid level : 11
> wp : yes
> flags : fpu de tsc msr pae cx8 apic sep cmov pat clflush acpi
> mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc up rep_good nopl
> nonstop_tsc aperfmperf pni ssse3 cx16 sse4_1 sse4_2 popcnt hypervisor
> lahf_lm dts
> bogomips : 4555.21
> clflush size : 64
> cache_alignment : 64
> address sizes : 40 bits physical, 48 bits virtual
> power management:
>
> # java -version
> java version "1.7.0_b147-icedtea"
> OpenJDK Runtime Environment (suse-1.2-x86_64)
> OpenJDK 64-Bit Server VM (build 22.0-b10, mixed mode)
>
>
> -------------
>
> Test results:
>
>
> Following JAVA_OPTS are used for both versions:
> -Xmx512m -Xms256m -XX:MaxPermSize=256m
>
>
>
> geronimo-tomcat6-javaee5-2.2.1
>
> ___________________________________________________________________________________________________________________________
>
>
> startup(From geronimo.out):
> Startup completed in 1:46.803s seconds
>
> list modules
> # time /$GERONIMO_HOME/bin/deploy.sh -u system -p manager list-modules
> ...
> real 0m13.703s
> user 0m9.617s
> sys 0m0.648s
>
>
> deploy
> # time $GERONIMO_HOME/bin/deploy.sh -u system -p manager deploy --inPlace
> ...
> real 0m12.815s
> user 0m9.137s
> sys 0m0.740s
>
> undeploy:
> # time $GERONIMO_HOME/bin/deploy.sh -u system -p manager undeploy
> org.apache.geronimo.samples/HelloWorldApp/1.0/war
> ...
> real 0m13.562s
> user 0m10.457s
> sys 0m0.840s
>
>
> CPU usage during deploy list-modules:
> geronimo: 0-20%
> deploy: 50-90%
>
> ___________________________________________________________________________________________________________________________
>
>
>
>
>
> geronimo-tomcat7-javaee6-3.0.03.0.0-20120620.212946 (I originally tested
> with 3.0.0-beta1 but snapshot was recommended to me by kevan)
>
> ___________________________________________________________________________________________________________________________
>
> startup(From geronimo.out):
> "Startup completed in 2:20.080s seconds"
>
>
> list modules:
> time $GERONIMO_HOME/bin/deploy -u system -p manager list-modules
> ...
> real 0m51.848s
> user 0m36.230s
> sys 0m3.376s
>
>
> deploy:
> time $GERONIMO_HOME/bin/deploy -u system -p manager deploy --inPlace .
> ...
> real 0m56.284s
> user 0m32.822s
> sys 0m3.680s
>
>
> undeploy:
> time $GERONIMO_HOME/bin/deploy -u system -p manager undeploy
> org.apache.geronimo.samples/HelloWorldApp/1.0/war
> ...
> real 0m47.336s
> user 0m32.862s
> sys 0m2.764s
>
>
>
> CPU usage during deploy list-modules:
> geronimo: 80-90%
> deploy: 10-20%
>
>
> ___________________________________________________________________________________________________________________________
>
--
Thanks!
Regards, Forrest