1 .. This work is licensed under a
2 .. Creative Commons Attribution 4.0 International License.
3 .. http://creativecommons.org/licenses/by/4.0
10 ##########################
12 Performance Test of Policy XACML PDP
13 ************************************
15 The Performance test was executed by performing requests
16 against the Policy RESTful APIs residing on the XACML PDP installed on a Cloud based Virtual Machine.
23 ONAP was deployed using a K8s Configuration on the same VM.
24 Running jmeter and ONAP OOM on the same VM may adversely impact the performance of the XACML-PDP being tested.
29 The Performance test was executed, and the result analyzed, via:
33 jmeter -Jduration=1200 -Jusers=10 \
34 -Jxacml_ip=$ip -Jpap_ip=$ip -Japi_ip=$ip \
35 -Jxacml_port=30111 -Jpap_port=30197 -Japi_port=30664 \
36 -n -t perf.jmx -l testresults.jtl
38 Note: the ports listed above correspond to port 6969 of the respective components.
40 The performance test, perf.jmx, runs the following, all in parallel:
42 - Healthcheck, 10 simultaneous threads
43 - Statistics, 10 simultaneous threads
44 - Decisions, 10 simultaneous threads, each running the following in sequence:
47 - Monitoring Decision, abbreviated
49 - Optimization Decision
50 - Default Guard Decision (always "Permit")
51 - Frequency Limiter Guard Decision
52 - Min/Max Guard Decision
54 When the script starts up, it uses policy-api to create, and policy-pap to deploy,
55 the policies that are needed by the test. It assumes that the "naming" policy has
56 already been created and deployed. Once the test completes, it undeploys and deletes
57 the policies that it previously created.
62 The test was run for 20 minutes at a time, for different numbers of users (i.e.,
63 threads), with the following results:
66 :header: "Number of Users", "Throughput (requests/second)", "Average Latency (ms)"
74 Stability Test of Policy XACML PDP
75 ************************************
77 The stability test was executed by performing requests
78 against the Policy RESTful APIs residing on the XACML PDP installed in the citycloud
79 lab. This was running on a kubernetes pod having the following configuration:
85 The test was run via jmeter, which was installed on the same VM.
86 Running jmeter and ONAP OOM on the same VM may adversely impact the performance of the XACML-PDP being tested.
87 Due to the minimal nauture of this setup, the K8S cluster became overloaded on a couple of occasions during the test.
88 This resulted in a small number of errors and a greater maximum transaction time than normal.
93 The stability test was performed on a default ONAP OOM installation in the city Cloud Lab environment.
94 JMeter was installed on the same VM to inject the traffic defined in the
95 `XACML PDP stability script
96 <https://git.onap.org/policy/xacml-pdp/tree/testsuites/stability/src/main/resources/testplans/stability.jmx>`_
97 with the following command:
101 jmeter.sh -Jduration=259200 -Jusers=2 -Jxacml_ip=$ip -Jpap_ip=$ip -Japi_ip=$ip \
102 -Jxacml_port=30111 -Jpap_port=30197 -Japi_port=30664 --nongui --testfile stability.jmx
104 Note: the ports listed above correspond to port 6969 of the respective components.
106 The default log level of the root and org.eclipse.jetty.server.RequestLog loggers in the logback.xml
108 (om/kubernetes/policy/components/policy-xacml-pdp/resources/config/logback.xml)
109 was set to WARN since the OOM installation did have log rotation enabled of the
110 container logs in the kubernetes worker nodes.
112 The stability test, stability.jmx, runs the following, all in parallel:
114 - Healthcheck, 2 simultaneous threads
115 - Statistics, 2 simultaneous threads
116 - Decisions, 2 simultaneous threads, each running the following tasks in sequence:
117 - Monitoring Decision
118 - Monitoring Decision, abbreviated
120 - Optimization Decision
121 - Default Guard Decision (always "Permit")
122 - Frequency Limiter Guard Decision
123 - Min/Max Guard Decision
125 When the script starts up, it uses policy-api to create, and policy-pap to deploy
126 the policies that are needed by the test. It assumes that the "naming" policy has
127 already been created and deployed. Once the test completes, it undeploys and deletes
128 the policies that it previously created.
133 The stability summary results were reported by JMeter with the following summary line:
137 summary = 222450112 in 72:00:39 = 858.1/s Avg: 5 Min: 1 Max: 946942 Err: 17 (0.00%)
139 The XACML PDP offered good performance with JMeter for the traffic mix described above, using 858 threads per second
140 to inject the traffic load. A small number of errors were encountered, and no significant CPU spikes were noted.
141 The average transaction time was 5ms. with a maximum of 946942ms.