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

[Richard Achmatowicz (JIRA)]

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

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

Adding the parameter -XX:MaxMetaspaceSize=256m (as in the Wildfly startup) 'fixes' the problem with the tenuredGen mentioned above. Now the tenturedGen values for both EAP6 and EAP7 are in line with each other, ranging between 400Mb - 600Mb during the performance test run. I'm rerunning the test without verbose GC to see if the performance is any better.

CORRECTION: I did a further run and the issue is back again even with the new setting. So it didn't fix it.


was (Author: rachmato):
Adding the parameter -XX:MaxMetaspaceSize=256m (as in the Wildfly startup) 'fixes' the problem with the tenuredGen mentioned above. Now the tenturedGen values for both EAP6 and EAP7 are in line with each other, ranging between 400Mb - 600Mb during the performance test run. I'm rerunning the test without verbose GC to see if the performance is any better.

> 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)