[jboss-jira] [JBoss JIRA] (WFLY-5822) Clustering performance regression in ejbremote-dist-sync scenario

Richard Achmatowicz (JIRA) issues at jboss.org
Wed Jan 20 15:48:00 EST 2016


    [ https://issues.jboss.org/browse/WFLY-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151403#comment-13151403 ] 

Richard Achmatowicz edited comment on WFLY-5822 at 1/20/16 3:47 PM:
--------------------------------------------------------------------

I have done a quick totaling of the total memory used in EAP 6 stress-ejbservlet-repl-sync and the corresponding EAP7 job.
This was done by turning on jvm stats, doing a grep on "Total value:" (the jvm stats field showing total memory used) and averaging over the number of records.

The averages for EAP6: 
perf32: 1263, with peaks into 2000's
perf33: 1289, with peaks into 2000's

The averages for EAP7: 
perf32: 1114, with peaks into 6000's
perf33: 3357, with peaks into 6000's



was (Author: rachmato):
I have done a quick totaling of the total memory used in EAP 6 stress-ejbservlet-repl-sync and the corresponding EAP7 job.
This was done by turning on jvm stats, doing a grep on "Total value:" (the jvm stats field showing total memory used) and averaging over the number of records.

The average for EAP6: 1280, with peaks into the 2000's
The average for EAP7: 3357, with peaks into the 6000's
 

> 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-stress-ejbremote-dist-sync/4/artifact/report/graph-throughput.png]
> 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-stress-ejbremote-dist-sync_noperf21/1/artifact/report/graph-throughput.png]
> ---------------------------------------
> 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-stress-ejbremote-repl-sync/3/artifact/report/graph-throughput.png]
> 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-stress-ejbremote-repl-sync_noperf21/2/artifact/report/graph-throughput.png]



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list