diff options
Diffstat (limited to 'docs/development/devtools/xacml-s3p.rst')
| -rw-r--r-- | docs/development/devtools/xacml-s3p.rst | 68 |
1 files changed, 48 insertions, 20 deletions
diff --git a/docs/development/devtools/xacml-s3p.rst b/docs/development/devtools/xacml-s3p.rst index 74369fc2..1411f90b 100644 --- a/docs/development/devtools/xacml-s3p.rst +++ b/docs/development/devtools/xacml-s3p.rst @@ -7,22 +7,20 @@ .. toctree:: :maxdepth: 2 -Policy XACML PDP component ########################## -Both the Performance and the Stability tests were 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: +Performance Test of Policy XACML PDP +************************************ + +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. +VM Configuration: - 16GB RAM - 8 VCPU -- 160GB Disk - -Both tests were run via jmeter, which was installed on a separate VM so-as not -to impact the performance of the XACML-PDP being tested. +- 1TB Disk -Performance Test of Policy XACML PDP -************************************ +ONAP was deployed using a K8s Configuration on a separate VM. Summary ======= @@ -34,9 +32,7 @@ The Performance test was executed, and the result analyzed, via: jmeter -Jduration=1200 -Jusers=10 \ -Jxacml_ip=$ip -Jpap_ip=$ip -Japi_ip=$ip \ -Jxacml_port=31104 -Jpap_port=32425 -Japi_port=30709 \ - -n -t perf.jmx - - ./result.sh + -n -t perf.jmx -l testresults.jtl Note: the ports listed above correspond to port 6969 of the respective components. @@ -68,15 +64,26 @@ threads), with the following results: .. csv-table:: :header: "Number of Users", "Throughput (requests/second)", "Average Latency (ms)" - 10, 6064, 4.1 - 20, 6495, 7.2 - 40, 6457, 12.2 - 80, 5803, 21.3 + 10, 8929, 3.10 + 20, 10827, 5.05 + 40, 11800, 9.35 + 80, 11750, 18.62 Stability Test of Policy XACML PDP ************************************ +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: + +- 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 ======= @@ -91,21 +98,42 @@ with the following command: 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 +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 container logs in the kubernetes worker nodes. +The stability test, stability.jmx, runs the following, all in parallel: + +- Healthcheck, 2 simultaneous threads +- Statistics, 2 simultaneous threads +- Decisions, 2 simultaneous threads, each running the following tasks in sequence: + - Monitoring Decision + - Monitoring Decision, abbreviated + - Naming Decision + - Optimization Decision + - Default Guard Decision (always "Permit") + - Frequency Limiter Guard Decision + - Min/Max Guard Decision + +When the script starts up, it uses policy-api to create, and policy-pap to deploy +the policies that are needed by the test. It assumes that the "naming" policy has +already been created and deployed. Once the test completes, it undeploys and deletes +the policies that it previously created. + Results ======= -The stability summary results were reported by JMeter with the following line: +The stability summary results were reported by JMeter with the following summary line: .. code-block:: bash - 2020-10-23 19:44:31,515 INFO o.a.j.r.Summariser: summary = 1061746369 in 72:00:16 = 4096.0/s Avg: 0 Min: 0 Max: 2584 Err: 0 (0.00%) + summary = 207771010 in 72:00:01 = 801.6/s Avg: 6 Min: 0 Max: 411 Err: 0 (0.00%) -The XACML PDP offered good performance with JMeter for the traffic mix described above, creating 4096 threads per second +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. |