Uploaded image for project: 'JBoss Remoting (3+)'
  1. JBoss Remoting (3+)
  2. REM3-317

[wildfly]jmx invocation performance with Wildfly9 degraded compared to JBoss42

XMLWordPrintable

    • Hide

      Can reproduce in my environment.
      1. Deploy the mbean notifiableMBeanjboss42.sar in the JBoss4.2 server and deploy notifiableMBeanwildfly.jar in the Wildfly9.0.2 server
      2. Call mbean from the local client (StandaloneInvoker.java and StandaloneMBeanInvoker4JBoss42.java)

      Show
      Can reproduce in my environment. 1. Deploy the mbean notifiableMBeanjboss42.sar in the JBoss4.2 server and deploy notifiableMBeanwildfly.jar in the Wildfly9.0.2 server 2. Call mbean from the local client (StandaloneInvoker.java and StandaloneMBeanInvoker4JBoss42.java)

      We switch our application server from JBoss4.2 to wildfly9.0.1 recently. After some testing, we found the JMX call performance degrade a lot.
      Take following test method as example, we use it to send one string array, the array size can vary, and each string length can change.
      public void perfWithStringArray(String[] events)
      The client and the MBean server are located in the same machine. Please take a look at the performance data

      StringLength*ArrayLength EPS(JBoss42) EPS(Wildfly9.01)
      128*200 300000 65000
      128*500 365000 80000
      512*500 126000 25000
      1024*500 67000 12000
      1024*5000 67000 12000

      The last two columns mean how many event could be handled in one second. You can see the performance degrades a lot.

              Unassigned Unassigned
              lcheng_nj_jira liang cheng (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: