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

Performance regression - remote JNDI lookup

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.1.0.CR1
    • 7.1.0.DR16, 7.1.0.ER3
    • Naming, 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#testLookupsSimpleIntPerformance -DfailIfNoTests=false -Deap=7x  | tee 
or 
mvn clean test -Dtest=RemoteJNDILookupPerfTestCase#testLookupsQueuePerformance -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#testLookupsSimpleIntPerformance -DfailIfNoTests= false -Deap=7x | tee or mvn clean test -Dtest=RemoteJNDILookupPerfTestCase#testLookupsQueuePerformance -DfailIfNoTests= false -Deap=7x | tee log Test does not fail - check test log for performance result.

    Description

      This continuation from jira JBEAP-10520 to track performance regression when looking up objects from remote server.

      For example if JMS queues are looked up then EAP 7.0.5.CP has performance 3333 lookups/second but EAP 7.1.0.ER3 has 1071 lookups/second. There is ~60% performance degradation. In case that simple integer is looked up then perf drop is from 3750 to 1578 lookups/second.

      Customer impact: Client application may time out when performing JNDI lookups for example during setup phase. If client application is regularly performing JNDI lookups for different objects then it will slow down the whole application.

      This is regression against EAP 7.0.

      Attachments

        Issue Links

          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-12605 Upgrade to naming client 1.0.1.Final

          • 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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10520 Performance issue - remote JNDI lookups of JMS connection factory

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: