[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=13157856#comment-13157856 ] 

Richard Achmatowicz commented on WFLY-5822:
-------------------------------------------

I've done an informal measurement of individual invocation response times from the client side by:
(i) instrumenting each EJBClient invocation to measure the time taken to process invoke() and writing that value to sysout on the client node 
(ii)  collecting up all such measurements on each client and averaging them

Here are the results:
[TIMING] method invocation took 359 ms
[TIMING] method invocation took 333 ms
[TIMING] method invocation took 365 ms
[TIMING] method invocation took 378 ms
[TIMING] method invocation took 388 ms
[TIMING] method invocation took 360 ms
[TIMING] method invocation took 403 ms
[TIMING] method invocation took 316 ms
[TIMING] method invocation took 342 ms
[TIMING] method invocation took 360 ms
[NOTE: these measurements above are not indicative of what happens later on in the test]
.....

-bash-4.2$ cat eap-7x-perf30-timing.txt | awk '{print $5}' | awk '{count+=$1;recs+=1} END {print count/recs " " recs}'
150.916 15786362
-bash-4.2$ cat eap-7x-perf31-timing.txt | awk '{print $5}' | awk '{count+=$1;recs+=1} END {print count/recs " " recs}'
148.895 15676367

----------------------------------
[TIMING] method invocation took 198 ms
[TIMING] method invocation took 197 ms
[TIMING] method invocation took 195 ms
[TIMING] method invocation took 211 ms
[TIMING] method invocation took 209 ms
[TIMING] method invocation took 201 ms
[TIMING] method invocation took 213 ms
[TIMING] method invocation took 214 ms
[TIMING] method invocation took 215 ms
[NOTE: these measurements above are not indicative of what happens later on in the test]

-bash-4.2$ cat eap-6x-perf30-timing.txt | awk '{print $5}' | awk '{count+=$1;recs+=1} END {print count/recs " " recs}'
346.394 8957198
-bash-4.2$ cat eap-6x-perf31-timing.txt | awk '{print $5}' | awk '{count+=$1;recs+=1} END {print count/recs " " recs}'
346.85 8814924

This is both with JDK 8.


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