[ https://issues.jboss.org/browse/WFLY-5822?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on WFLY-5822: ------------------------------------------- I did a quick check on the speed at which invocations are being processed in servers, once they arrive. When an invocation is unpacked, a call is made to MethodInvocationMessageHandler to perform the invocation, which is performed in a separate thread in a runnable. I instrumented start ms and stop ms and printed out (stop-start) ms line, both for EAP 6.4.0 and EAP 7.0.0. Here are the results: {noformat} // EAP 6.4.0 run (https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/rachmatowicz___bytem...) [nrla@lenovo 1]$ grep MethodInvocationMessageHandler perf18.log | awk '{sum+=$16;recs+=1} END {print recs " " sum/recs}' 7401445 1.7345 [nrla@lenovo 1]$ grep MethodInvocationMessageHandler perf18.log | awk '{sum+=$16;recs+=1} END {print recs " " sum/recs}' 7401445 1.7345 [nrla@lenovo 1]$ grep MethodInvocationMessageHandler perf19.log | awk '{sum+=$16;recs+=1} END {print recs " " sum/recs}' 7330766 1.77929 [nrla@lenovo 1]$ grep MethodInvocationMessageHandler perf20.log | awk '{sum+=$16;recs+=1} END {print recs " " sum/recs}' 7165113 1.80155 // EAP 7.0.0 run, number 6 [nrla@lenovo 6]$ grep MethodInvocationMessageHandler perf18.log | awk '{sum+=$16;recs+=1} END {print recs " " sum/recs}' 8589348 2.20701 [nrla@lenovo 6]$ grep MethodInvocationMessageHandler perf19.log | awk '{sum+=$16;recs+=1} END {print recs " " sum/recs}' 6827447 2.96184 [nrla@lenovo 6]$ grep MethodInvocationMessageHandler perf20.log | awk '{sum+=$16;recs+=1} END {print recs " " sum/recs}' 8718950 2.17151 {noformat}// EAP 6.4.0 run, number 1 [nrla@lenovo 1]$ grep MethodInvocationMessageHandler perf18.log | awk '{sum+=$16;recs+=1} END {print recs sum/recs}' 74014451.7345 [nrla@lenovo 1]$ grep MethodInvocationMessageHandler perf18.log | awk '{sum+=$16;recs+=1} END {print recs " " sum/recs}' 7401445 1.7345 [nrla@lenovo 1]$ grep MethodInvocationMessageHandler perf19.log | awk '{sum+=$16;recs+=1} END {print recs " " sum/recs}' 7330766 1.77929 [nrla@lenovo 1]$ grep MethodInvocationMessageHandler perf20.log | awk '{sum+=$16;recs+=1} END {print recs " " sum/recs}' 7165113 1.80155 // EAP 7.0.0 run () [nrla@lenovo 6]$ grep MethodInvocationMessageHandler perf18.log | awk '{sum+=$16;recs+=1} END {print recs " " sum/recs}' 8589348 2.20701 [nrla@lenovo 6]$ grep MethodInvocationMessageHandler perf19.log | awk '{sum+=$16;recs+=1} END {print recs " " sum/recs}' 6827447 2.96184 [nrla@lenovo 6]$ grep MethodInvocationMessageHandler perf20.log | awk '{sum+=$16;recs+=1} END {print recs " " sum/recs}' 8718950 2.17151 There doesn't seem to be a great deal of difference in the time it takes to process an invocation once it has arrived: rougfhly 1.7 ms for EAP 6 and 2.4 for EAP 7. Given that EAP 7 has a few mote cache operations per invocation, this makes sense. However, looking at the corresponding throughput data, EAP 6 seems to be handling many more requests than EAP 7. -- This message was sent by Atlassian JIRA (v6.4.11#64026)