Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-10520

Performance issue - remote JNDI lookups of JMS connection factory

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • 7.1.0.DR16, 7.1.0.DR18, 7.1.0.ER2
    • ActiveMQ, Remoting
    • None
    • Regression
    • Hide

      To run the benchmark test:

      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout jndi-perf-issue

groovy -DEAP_VERSION=7.1.0.ER3 PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap

cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest=RemoteJNDILookupPerfTestCase#testLookupsCFPerformance -DfailIfNoTests=false -Deap=7x  | tee log

      Test does not fail - check test log for performance result.

      Show
      To run the benchmark test: git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ git checkout jndi-perf-issue groovy -DEAP_VERSION=7.1.0.ER3 PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn clean test -Dtest=RemoteJNDILookupPerfTestCase#testLookupsCFPerformance -DfailIfNoTests= false -Deap=7x | tee log Test does not fail - check test log for performance result.

    Description

      There is regression in performance when client makes remote JNDI lookup to server. Lookup in EAP 7.1.DR16 takes ~2x more time than in EAP 7.0.5.

      Customer Impact: If customer application has configured timeouts for tasks which include remote JNDI lookups then those tasks may start to timeout after migration from EAP 7.0 to EAP 7.1. This will behave like if server is unresponsive.

      Change in behavior was detected in SpecJMS2007 benchmark where number of JMS clients is using one instance of javax.naming.Context to lookup JMS queues/topics. Benchmark timed out in this phase.

      By writing simple performance test where 1 client makes 20 000 JNDI lookups for queue in sequence, lookups/second performance for EAP 7.1.0.DR16 is approximatally 2 times worse than with EAP 7.0.5.

        EAP 7.0.5.CP EAP 7.1.0.DR16
      lookups/second 119 64

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-12574 Performance regression - remote JNDI lookup

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9272 EJB client performance drop in EAP 7.1

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified

          Activity

            People

              mtaylor1@redhat.com Martyn Taylor (Inactive)
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: