**apex-pdp VM details**
-OS:Ubuntu 16.04.5 LTS
+OS:Ubuntu 18.04 LTS
CPU: 4 core
HardDisk: 40 GB
-Docker Version: 18.06.1-ce, build e68fc7a
+Docker Version: 19.03.8, build afacb8b7f0
-Java: openjdk version "1.8.0_181"
+Java: openjdk version "11.0.7"
**JMeter VM details**
-OS: Ubuntu 16.04.3 LTS
+OS: Ubuntu 18.04 LTS
CPU: 4 core
HardDisk: 40 GB
-Java: openjdk version "1.8.0_181"
+Java: openjdk version "11.0.7"
-JMeter: 5.1.1
+JMeter: 5.2.1
Install JMeter in virtual machine
---------------------------------
Make the etc/hosts entries
.. code-block:: bash
-
+
echo $(hostname -I | cut -d\ -f1) $(hostname) | sudo tee -a /etc/hosts
-
+
Make the DNS entries
.. code-block:: bash
echo "nameserver <PrimaryDNSIPIP>" >> sudo /etc/resolvconf/resolv.conf.d/head
-
+
echo "nameserver <SecondaryDNSIP>" >> sudo /etc/resolvconf/resolv.conf.d/head
-
+
resolvconf -u
Update the ubuntu software installer
.. code-block:: bash
apt-get update
-
+
Check & Install Java
.. code-block:: bash
- apt-get install -y openjdk-8-jdk
-
+ apt-get install -y openjdk-11-jdk
+
java -version
Download & install JMeter
.. code-block:: bash
mkdir jMeter
-
-
+
+
cd jMeter
-
-
- wget http://mirrors.whoishostingthis.com/apache//jmeter/binaries/apache-jmeter-5.1.1.zip
-
-
- unzip apache-jmeter-5.1.1.zip
+
+
+ wget http://mirrors.whoishostingthis.com/apache//jmeter/binaries/apache-jmeter-5.2.1.zip
+
+
+ unzip apache-jmeter-5.2.1.zip
Install apex-pdp in virtual machine
-----------------------------------
.. code-block:: bash
echo $(hostname -I | cut -d\ -f1) $(hostname) | sudo tee -a /etc/hosts
-
+
2. Make the DNS entries
.. code-block:: bash
.. code-block:: bash
- apt-get install -y openjdk-8-jdk
+ apt-get install -y openjdk-11-jdk
java -version
Ensure that the Java version that is executing is OpenJDK version 8
.. code-block:: bash
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
- add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
- apt-get update
- apt-cache policy docker-ce
- apt-get install -y docker-ce
- systemctl status docker
- docker ps
-
-6. Change the permissions of the Docker socket file
+ sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
+ sudo apt-get update
+ sudo apt-cache policy docker-ce
+ sudo apt-get install -y docker-ce
+ sudo systemctl enable docker
+ sudo systemctl start docker
+ sudo usermod -aG docker <your user id>
-.. code-block:: bash
-
- chmod 777 /var/run/docker.sock
+6. Logout and re-login to ensure the ``usermod`` command takes effective
7. Check the status of the Docker service and ensure it is running correctly
.. code-block:: bash
- service docker status
docker ps
**Install apex-pdp**
.. code-block:: bash
- docker run -d --name apex -p 12561:12561 -p 23324:23324 -it nexus3.onap.org:10001/onap/policy-apex-pdp:2.1.0-latest /bin/bash -c "/opt/app/policy/apex-pdp/bin/apexApps.sh jmx-test -c /opt/app/policy/apex-pdp/examples/config/SampleDomain/RESTServerJsonEvent.json"
+ docker run -d --name apex -p 12561:12561 -p 23324:23324 -p 9911:9911 nexus3.onap.org:10001/onap/policy-apex-pdp:2.3.1 /bin/bash -c "/opt/app/policy/apex-pdp/bin/apexApps.sh jmx-test -c /opt/app/policy/apex-pdp/examples/config/SampleDomain/RESTServerJsonEvent.json"
docker ps
Note: If you observe that requests from JMeter client is failing due to timeout, then modify the "RESTServerJsonEvent.json" mentioned in the above command and increase the "synchronousTimeout" property as per needed.
sudo apt-get install visualvm
-Login to docker container (using root)
-
-.. code-block:: bash
-
- docker exec -u 0 -it apex /bin/bash
-
-Run few commands to configure permissions
-
-.. code-block:: bash
-
- cd /usr/lib/jvm/java-1.8-openjdk/bin/
-
- touch visualvm.policy
-
- vi visualvm.policy
-
- Add the following in visualvm.policy
-
-
- grant codebase "file:/usr/lib/jvm/java-1.8-openjdk/lib/tools.jar" {
- permission java.security.AllPermission;
- };
-
-
- chmod 777 visualvm.policy
-
-
- exit
-
-Login to docker container (using normal user)
-
-.. code-block:: bash
-
- docker exec -it apex /bin/bash
-
-Run following commands to start jstatd using port 1111
-
-.. code-block:: bash
-
- cd /usr/lib/jvm/java-1.8-openjdk/bin/
-
-
- ./jstatd -p 1111 -J-Djava.security.policy=visualvm.policy &
-
-
- exit
-
Login to VM using graphical interface in separate terminal window.
.. code-block:: bash
.. code-block:: bash
visualvm &
-
-Connect to jstatd & remote apex-pdp JVM
-
-1. Right click on "Remote" in the left panel of the screen and select "Add Remote Host..."
-2. Enter the IP address of apex-pdp docker container.
-
-.. code-block:: bash
-
- docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' container_name_or_id
-
-3. Right click on IP address, select "Add jstatd Connection..."
-4. In "jstatd Connections" tab, enter port 1111 and click OK.
-5. Right click on IP address, select "Add JMX Connection..."
-6. Enter the apex-pdp docker container IP Address (from step 2) <IP address>:9911 ( for example - 172.17.0.2:9911) and click OK.
-7. Double click on the newly added nodes under "Remote" to start monitoring CPU, Memory & GC.
+Connect to apex-pdp JVM's JMX agent
+1. Right click on "Local" in the left panel of the screen and select "Add Local JMX Connection..."
+2. Enter localhost:9911 for "Connection", and click OK
+3. Double click on the newly added nodes under "Local" to start monitoring CPU, Memory & GC.
Sample Screenshot of visualVM
-.. image:: images/apex-s3p-vvm-sample.jpg
+.. image:: images/stability-visualvm1.PNG
+.. image:: images/stability-visualvm2.PNG
Test Plan
---------
.. code-block:: bash
- ~/jMeter/apache-jmeter-5.1.1/bin/jmeter -g stability.log -o ./result/
+ ~/jMeter/apache-jmeter-5.2.1/bin/jmeter -g stability.log -o ./result/
+
+============================================== =================================================== ================================ ============= ============
+**Number of Client Threads running in JMeter** **Number of Server Threads running in Apex engine** **Total number of input events** **Success %** **Error %**
+============================================== =================================================== ================================ ============= ============
+20 4 8594220 100% 0%
+============================================== =================================================== ================================ ============= ============
+
+.. image:: images/stability-jmeter.PNG
+
+:download:`result.zip <zip/result.tar>`
+
+
+Frankfurt release
+^^^^^^^^^^^^^^^^^^
+
+The 72 hour Stability Test for apex-pdp has the goal of introducing a steady flow of transactions using jMeter.
+
+The input event will be submitted through the rest interface of DMaaP , which then triggers a grpc request to CDS. Based on the response, another DMaaP event is triggered.
+
+This test will be performed in an OOM deployment setup. The test will be performed in a multi-threaded environment where 5 threads running in JMeter will keep sending events for the duration of 72 hours.
+
+Test Plan Frankfurt release
+---------------------------
+
+The 72 hours stability test will run the following steps in a 5 threaded loop.
+
+- **Create Policy** - creates a policy using the policy/api component
+- **Deploy Policy** - deploys the policy in the existing PdpGroup
+- **Check Health** - checks the health status of apex
+- **Send Input Event** - trigger 'unauthenticated.DCAE_CL_OUTPUT' event of DMaaP.
+- **Get Output Event Response** - check for the triggered output event.
+- **Undeploy Policy** - undeploys the policy from PdpGroup
+- **Delete Policy** - deletes the policy using the policy/api component
+
+The following steps can be used to configure the parameters of the test plan.
+
+- **HTTP Header Manager** - used to store headers which will be used for making HTTP requests.
+- **HTTP Request Defaults** - used to store HTTP request details like Server Name or IP, Port, Protocol etc.
+- **User Defined Variables** - used to store the following user defined parameters:
+
+================== ============================================================================ ============================
+**Name** **Description** **Default Value**
+================== ============================================================================ ============================
+wait Wait time after each request (in milliseconds) 120000
+threads Number of threads to run test cases in parallel. 5
+threadsTimeOutInMs Synchronization timer for threads running in parallel (in milliseconds). 150000
+================== ============================================================================ ============================
+
+
+Download and update the jmx file presented in the apex-pdp git repository - `jmx file path <https://gerrit.onap.org/r/gitweb?p=policy/apex-pdp.git;a=tree;f=testsuites/apex-pdp-stability/src/main/resources;h=99d373033a190a690d4e05012bc3a656cae7bc3f;hb=refs/heads/master>`_.
+
+- HTTPSampler.domain - The ip address of the VM in which the apex container is running
+- HTTPSampler.port - The listening port, here is 23324
+- ThreadGroup.druation - Set the duration to 72 hours (in seconds)
+
+Use the CLI mode to start the test
+
+.. code-block:: bash
+
+ ./jmeter.sh -n -t ~/apexPdpStabilityTestPlan.jmx -Jusers=1 -l ~/stability.log
+
+
+Stability Test Results Frankfurt release
+-----------------------------------------
+
+The stability test plan was triggered for 72 hours, injecting input events to apex-pdp from 5 client threads running in JMeter.
+
+After the test stops, we can generate an HTML test report via the command:
+
+.. code-block:: bash
+
+ ~/jMeter/apache-jmeter-5.2.1/bin/jmeter -g stability.log -o ./result/
============================================== =================================================== ================================ ============= ============
**Number of Client Threads running in JMeter** **Number of Server Threads running in Apex engine** **Total number of input events** **Success %** **Error %**
============================================== =================================================== ================================ ============= ============
-20 4 6394602 99.999971% 0.0029%
+5 4 26766 100% 0%
============================================== =================================================== ================================ ============= ============
-:download:`result.zip <zip/result.zip>`
-:download:`onap.zip <zip/onap.zip>`
+**VisualVM Screenshot**
+
+.. image:: images/frankfurt/apex_s3p_vm-1.png
+.. image:: images/frankfurt/apex_s3p_vm-2.png
+**JMeter Screenshot**
+
+.. image:: images/frankfurt/apex_s3p_jm-1.png
+.. image:: images/frankfurt/apex_s3p_jm-2.png
+
+:download:`result.zip <zip/frankfurt/apex_s3p_result.tar>`
Setting up Performance Tests in APEX
++++++++++++++++++++++++++++++++++++
-The apex-pdp has built in support for performance testing. A special performance testing REST server is available in the code base for performance testing.
-It is in the module `performance-benchmark-test <https://github.com/onap/policy-apex-pdp/tree/master/testsuites/performance/performance-benchmark-test>`_.
-To execute a benchmark test, you start the REST server, and then configure and run APEX against the server.
+The apex-pdp has built in support for performance testing. A special performance testing REST server is available in the code base for performance testing.
+It is in the module `performance-benchmark-test <https://github.com/onap/policy-apex-pdp/tree/master/testsuites/performance/performance-benchmark-test>`_.
+To execute a benchmark test, you start the REST server, and then configure and run APEX against the server.
There are example configurations for running tests in the `resources of this module <https://github.com/onap/policy-apex-pdp/tree/master/testsuites/performance/performance-benchmark-test/src/main/resources/examples/benchmark>`_.
In order to run the test for 72 hours, set the batch count in the `EventGeneratorConfig.json <https://github.com/onap/policy-apex-pdp/blob/master/testsuites/performance/performance-benchmark-test/src/main/resources/examples/benchmark/EventGeneratorConfig.json>`_ file to zero, which causes the REST server to generate batches forever.
mkdir apex
cd apex
tar zxvf ~/git/onap/policy/apex-pdp/packages/apex-pdp-package-full/target/*gz
-
+
4. Run APEX with a configuration that runs against the benchmark REST server, select the configuration that is appropriate for the number of threads for the number of cores on the host on which APEX is running. For example on a 32 core machine, select the "32" configuration, on an 8 core machine, select the "08" configuration.
.. code-block:: bash
bin/apexApps.sh engine -c ~/git/onap/policy/apex-pdp/testsuites/performance/performance-benchmark-test/src/main/resources/examples/benchmark/Javascript64.json
-
+
5. To get the test results, Issue the following command using CURL or from a browser(also can store the result into a file by setting outfile in the `EventGeneratorConfig.json <https://github.com/onap/policy-apex-pdp/blob/master/testsuites/performance/performance-benchmark-test/src/main/resources/examples/benchmark/EventGeneratorConfig.json>`_ file, statistics would be written into this file after event generator terminated)
-
+
.. code-block:: bash
curl http://localhost:32801/EventGenerator/Stats
-
+
The results are similar to those below:
-
+
:download:`Example APEX performance metrics <json/example-apex-perf.json>`
-Performance Test Result
------------------------
+Performance Test Result Frankfurt
+---------------------------------
**Summary**
-Performance test was triggered for 2 hours on a 4 core, 4GB RAM virtual machine.
+Performance test was triggered for 2 hours on a 4 core, 4GB RAM virtual machine.
**Test Statistics**
-:download:`Attached result log <json/result.json>`
+:download:`Attached result log <json/frankfurt-apex-perf.json>`
=============== ============= ================= ============== ===================== ================== ============= ===========
**batchNumber** **batchSize** **eventsNotSent** **eventsSent** **eventsNotReceived** **eventsReceived** **Success %** **Error %**
=============== ============= ================= ============== ===================== ================== ============= ===========
-3650 182500 0 182500 0 182500 100 % 0 %
+-1 431250 0 431250 0 431250 100 % 0 %
=============== ============= ================= ============== ===================== ================== ============= ===========
======================== ========================= ========================
**averageRoundTripNano** **shortestRoundTripNano** **longestRoundTripNano**
======================== ========================= ========================
-40024623 7439158 5161374486
+148965724 20169907 429339393
======================== ========================= ========================
============================ ============================= ============================
**averageApexExecutionNano** **shortestApexExecutionNano** **longestApexExecutionNano**
============================ ============================= ============================
-1335622 513650 5104326434
+62451899 3901010 354528579
============================ ============================= ============================
Code Review / policy / parent.git / blobdiff