Details

    • Type: Bug
    • Status: Verified (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: 7.1.0.DR16, 7.1.0.ER3
    • Fix Version/s: 7.1.0.CR1
    • Component/s: Naming, Remoting
    • Labels:
      None
    • Target Release:
    • Steps to Reproduce:
      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.
    • Affects Testing:
      Regression

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jmesnil Jeff Mesnil
                  Reporter:
                  mnovak Miroslav Novak
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: