##########################
-Performance Test of Policy XACML PDP
-************************************
+Performance Test of Policy XACML PDP (Jakarta)
+**********************************************
The Performance test was executed by performing requests
-against the Policy RESTful APIs residing on the XACML PDP installed on a Cloud based Virtual Machine.
+against the Policy RESTful APIs.
+
+A default ONAP installation in the Policy tenant in UNH was used to run the tests.
+
+The Agent VMs in this lab have the following configuration:
-VM Configuration:
- 16GB RAM
- 8 VCPU
-- 1TB Disk
-
-ONAP was deployed using a K8s Configuration on a separate VM.
Summary
=======
-The Performance test was executed, and the result analyzed, via:
+The Performance test was executed, and the result analysed, via:
.. code-block:: bash
jmeter -Jduration=1200 -Jusers=10 \
-Jxacml_ip=$ip -Jpap_ip=$ip -Japi_ip=$ip \
- -Jxacml_port=31104 -Jpap_port=32425 -Japi_port=30709 \
+ -Jxacml_port=30111 -Jpap_port=30197 -Japi_port=30664 \
-n -t perf.jmx -l testresults.jtl
Note: the ports listed above correspond to port 6969 of the respective components.
-The performance test, perf.jmx, runs the following, all in parallel:
+The performance tests runs the following, all in parallel:
- Healthcheck, 10 simultaneous threads
- Statistics, 10 simultaneous threads
Results
=======
-The test was run for 20 minutes at a time, for different numbers of users (i.e.,
-threads), with the following results:
+The test was run for 20 minutes with 10 users (i.e., threads), with the following results:
.. csv-table::
:header: "Number of Users", "Throughput (requests/second)", "Average Latency (ms)"
- 10, 8929, 3.10
- 20, 10827, 5.05
- 40, 11800, 9.35
- 80, 11750, 18.62
+ 10, 4603, 2
+
+.. image:: images/s3p-perf-xacml.png
Stability Test of Policy XACML PDP
-************************************
+**********************************
+
+This test was run using jmeter on a default
+ONAP installation in the Policy tenant in UNH.
-The stability test was executed by performing requests
-against the Policy RESTful APIs residing on the XACML PDP installed in the windriver
-lab. This was running on a kubernetes pod having the following configuration:
+The Agent VMs in this lab have the following configuration:
- 16GB RAM
- 8 VCPU
-- 160GB Disk
-
-The test was run via jmeter, which was installed on a separate VM so-as not
-to impact the performance of the XACML-PDP being tested.
Summary
=======
-The stability test was performed on a default ONAP OOM installation in the Intel Wind River Lab environment.
-JMeter was installed on a separate VM to inject the traffic defined in the
+The stability test was performed on a default ONAP OOM installation in the Policy tenant of the UNH lab.
+JMeter injected the traffic defined in the
`XACML PDP stability script
<https://git.onap.org/policy/xacml-pdp/tree/testsuites/stability/src/main/resources/testplans/stability.jmx>`_
with the following command:
.. code-block:: bash
jmeter.sh -Jduration=259200 -Jusers=2 -Jxacml_ip=$ip -Jpap_ip=$ip -Japi_ip=$ip \
- -Jxacml_port=31104 -Jpap_port=32425 -Japi_port=30709 --nongui --testfile stability.jmx
+ -Jxacml_port=30111 -Jpap_port=30197 -Japi_port=30664 --nongui --testfile stability.jmx
Note: the ports listed above correspond to port 6969 of the respective components.
The default log level of the root and org.eclipse.jetty.server.RequestLog loggers in the logback.xml
of the XACML PDP
(om/kubernetes/policy/components/policy-xacml-pdp/resources/config/logback.xml)
-was set to ERROR since the OOM installation did not have log rotation enabled of the
+was set to WARN since the OOM installation did have log rotation enabled of the
container logs in the kubernetes worker nodes.
The stability test, stability.jmx, runs the following, all in parallel:
.. code-block:: bash
- summary = 207771010 in 72:00:01 = 801.6/s Avg: 6 Min: 0 Max: 411 Err: 0 (0.00%)
+ summary = 941639699 in 71:59:36 = 3633.2/s Avg: 1 Min: 0 Max: 842 Err: 0 (0.00%)
-The XACML PDP offered good performance with JMeter for the traffic mix described above, using 801 threads per second
-to inject the traffic load. No errors were encountered, and no significant CPU spikes were noted.
-The average transaction time was 6ms. with a maximum of 411ms.
+The XACML PDP offered very good performance with JMeter for the traffic mix described above.
+The average transaction time is insignificant. The maximum transaction time of 842 ms.
+There was a Drools stability test running in parallel, hence the actual load was higher.
Code Review / policy / parent.git / blobdiff