[
https://issues.jboss.org/browse/WFLY-5822?page=com.atlassian.jira.plugin....
]
Richard Achmatowicz edited comment on WFLY-5822 at 1/22/16 8:57 AM:
--------------------------------------------------------------------
In the clustering meeting yesterday, Rado mentioned that part of the difficulty here is
that we are comparing EAP6 source code + JDK 6 to EAP 7 source code + JDK 8, and that
there are big changes in heap management in JDK 6 vs JDK 8 (removal of permGen and
introduction of metaSpace).
So, we did a comparison of EAP 6 vs EAP 7 using the same JVM - JDK 8. Here are the results
(on two server nodes instead of four):
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mvinkler_eap-7x-stre...
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mvinkler_eap-6x-stres...
Using the same JVM, EAP 7 hits 13,000 reqs / sec versus EAP 6 hitting 10,000 reqs / sec.
Running the same 2 server test for EAP 6 using JDK 6 only yields marginally better
results:
was (Author: rachmato):
In the clustering meeting yesterday, Rado mentioned that part of the difficulty here is
that we are comparing EAP6 source code + JDK 6 to EAP 7 source code + JDK 8, and that
there are big changes in heap management in JDK 6 vs JDK 8 (removal of permGen and
introduction of metaSpace).
So, we did a comparison of EAP 6 vs EAP 7 using the same JVM - JDK 8. Here are the results
(on two server nodes instead of four):
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mvinkler_eap-7x-stre...
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mvinkler_eap-6x-stres...
Using the same JVM, EAP 7 hits 13,000 reqs / sec versus EAP 6 hitting 10,000 reqs / sec.
Clustering performance regression in ejbremote-dist-sync scenario
------------------------------------------------------------------
Key: WFLY-5822
URL:
https://issues.jboss.org/browse/WFLY-5822
Project: WildFly
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 10.0.0.CR5
Reporter: Michal Vinkler
Assignee: Richard Achmatowicz
Priority: Critical
Compared to EAP 6, all SYNC scenarios have the same/better performance except of this
one, wonder why?
Compare these results:
stress-ejbremote-dist-sync
7.0.0.ER2:
[
throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...]
6.4.0.GA:
[
throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...]
---------------------------------------
Just for comparison: ejbremote REPL_SYNC scenario *performs well* on the other hand:
stress-ejbremote-repl-sync
7.0.0.ER2:
[
throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...]
6.4.0.GA:
[
throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)