[jboss-jira] [JBoss JIRA] (WFLY-5822) Clustering performance regression in ejbremote-dist-sync scenario
[
https://issues.jboss.org/browse/WFLY-5822?page=com.atlassian.jira.plugin....
]
Richard Achmatowicz commented on WFLY-5822:
-------------------------------------------
The ejbservlet stress test scenario exercises SFSBs in a similar way as ejbremote, but
uses servlet requests instead of EJBClient requests to access the beans on the server.
We have done a run of the ejbservlet performance test for EAP6 and EAP7 using dist sync
with two cluster nodes instead of four (due to low current availability in the performance
lab). The results also show a regression of EAP7 with respect to EAP6:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mvinkler_eap-6x-stres...
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mvinkler_eap-7x-stres...
In EAP 6, the max throughput hits 8.5k requests at 2400 clients and more or less levels
out, whereas EAP7 hits a max of about 6k requests at 800 clients and then flatlines.
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)
