diff options
| -rw-r--r-- | docs/development/devtools/images/pap-s3p-jm-performance.JPG | bin | 486724 -> 0 bytes | |||
| -rw-r--r-- | docs/development/devtools/images/pap-s3p-jm-stability.JPG | bin | 553410 -> 0 bytes | |||
| -rw-r--r-- | docs/development/devtools/images/pap-s3p-mem-at.PNG | bin | 0 -> 16444 bytes | |||
| -rw-r--r-- | docs/development/devtools/images/pap-s3p-mem-bt.PNG | bin | 0 -> 17741 bytes | |||
| -rw-r--r-- | docs/development/devtools/images/pap-s3p-performance-result-jmeter.PNG | bin | 0 -> 114642 bytes | |||
| -rw-r--r-- | docs/development/devtools/images/pap-s3p-stability-result-jmeter.PNG | bin | 0 -> 145262 bytes | |||
| -rw-r--r-- | docs/development/devtools/images/pap-s3p-top-after.JPG | bin | 48456 -> 0 bytes | |||
| -rw-r--r-- | docs/development/devtools/images/pap-s3p-top-before.JPG | bin | 72351 -> 0 bytes | |||
| -rw-r--r-- | docs/development/devtools/pap-s3p.rst | 32 |
9 files changed, 16 insertions, 16 deletions
diff --git a/docs/development/devtools/images/pap-s3p-jm-performance.JPG b/docs/development/devtools/images/pap-s3p-jm-performance.JPG Binary files differdeleted file mode 100644 index 60bf6210..00000000 --- a/docs/development/devtools/images/pap-s3p-jm-performance.JPG +++ /dev/null diff --git a/docs/development/devtools/images/pap-s3p-jm-stability.JPG b/docs/development/devtools/images/pap-s3p-jm-stability.JPG Binary files differdeleted file mode 100644 index 58e26b5f..00000000 --- a/docs/development/devtools/images/pap-s3p-jm-stability.JPG +++ /dev/null diff --git a/docs/development/devtools/images/pap-s3p-mem-at.PNG b/docs/development/devtools/images/pap-s3p-mem-at.PNG Binary files differnew file mode 100644 index 00000000..b13a74f2 --- /dev/null +++ b/docs/development/devtools/images/pap-s3p-mem-at.PNG diff --git a/docs/development/devtools/images/pap-s3p-mem-bt.PNG b/docs/development/devtools/images/pap-s3p-mem-bt.PNG Binary files differnew file mode 100644 index 00000000..774d342d --- /dev/null +++ b/docs/development/devtools/images/pap-s3p-mem-bt.PNG diff --git a/docs/development/devtools/images/pap-s3p-performance-result-jmeter.PNG b/docs/development/devtools/images/pap-s3p-performance-result-jmeter.PNG Binary files differnew file mode 100644 index 00000000..19788e73 --- /dev/null +++ b/docs/development/devtools/images/pap-s3p-performance-result-jmeter.PNG diff --git a/docs/development/devtools/images/pap-s3p-stability-result-jmeter.PNG b/docs/development/devtools/images/pap-s3p-stability-result-jmeter.PNG Binary files differnew file mode 100644 index 00000000..8357b1d4 --- /dev/null +++ b/docs/development/devtools/images/pap-s3p-stability-result-jmeter.PNG diff --git a/docs/development/devtools/images/pap-s3p-top-after.JPG b/docs/development/devtools/images/pap-s3p-top-after.JPG Binary files differdeleted file mode 100644 index 967cdcc0..00000000 --- a/docs/development/devtools/images/pap-s3p-top-after.JPG +++ /dev/null diff --git a/docs/development/devtools/images/pap-s3p-top-before.JPG b/docs/development/devtools/images/pap-s3p-top-before.JPG Binary files differdeleted file mode 100644 index a922617f..00000000 --- a/docs/development/devtools/images/pap-s3p-top-before.JPG +++ /dev/null diff --git a/docs/development/devtools/pap-s3p.rst b/docs/development/devtools/pap-s3p.rst index ba9a74f6..1c031775 100644 --- a/docs/development/devtools/pap-s3p.rst +++ b/docs/development/devtools/pap-s3p.rst @@ -34,9 +34,12 @@ The 72 hours stability test ran the following steps sequentially in a single thr - **Change state to ACTIVE** - changes the state of defaultGroup PdpGroup to ACTIVE - **Check PdpGroup Query** - makes a PdpGroup query request and verifies that PdpGroup is in the ACTIVE state. - **Deploy defaultDomain Policy** - deploys the policy defaultDomain in the existing PdpGroup +- **Check status of defaultGroup** - checks the status of defaultGroup PdpGroup with the defaultDomain policy 1.0.0. - **Create/Update PDP Group** - creates a new PDPGroup named sampleGroup. - **Check PdpGroup Query** - makes a PdpGroup query request and verifies that 2 PdpGroups are in the ACTIVE state and defaultGroup has a policy deployed on it. - **Deployment Update sampleDomain** - deploys the policy sampleDomain in sampleGroup PdpGroup using pap api +- **Check status of sampleGroup** - checks the status of the sampleGroup PdpGroup. +- **Check status of PdpGroups** - checks the status of both PdpGroups. - **Check PdpGroup Query** - makes a PdpGroup query request and verifies that the defaultGroup has a policy defaultDomain deployed on it and sampleGroup has policy sampleDomain deployed on it. - **Check Consolidated Health** - checks the consolidated health status of all policy components. - **Check Deployed Policies** - checks for all the deployed policies using pap api. @@ -68,14 +71,14 @@ The test was run in the background via "nohup", to prevent it from being interru .. code-block:: bash - nohup ./jMeter/apache-jmeter-5.3/bin/jmeter.sh -n -t stability.jmx -l testresults.jtl + nohup ./jMeter/apache-jmeter-5.3/bin/jmeter.sh -n -t stabil.jmx -l testresults.jtl Test Results ------------ **Summary** -Stability test plan was triggered for 72 hours. +Stability test plan was triggered for 24 hours. .. Note:: @@ -92,20 +95,18 @@ Stability test plan was triggered for 72 hours. ======================= ================= ================== ================================== **Total # of requests** **Success %** **Error %** **Average time taken per request** ======================= ================= ================== ================================== -35059 99.99 % 0.01 % 354 ms +11921 100.00 % 0.00 % 382 ms ======================= ================= ================== ================================== .. Note:: .. container:: paragraph - There were only 3 failures during the 72 hours test, and all these 3 happened because the 2nd PDP instance didn't - get registered in time to the new group created, and as a result, the PdpGroup Query failed. This can be ignored, - as it was only a matter of one missing heartbeat over a period of 24 hours. + There were no failures during the 24 hours test. **JMeter Screenshot** -.. image:: images/pap-s3p-jm-stability.JPG +.. image:: images/pap-s3p-stability-result-jmeter.PNG **Memory and CPU usage** @@ -113,13 +114,12 @@ The memory and CPU usage can be monitored by running "top" command on the PAP po Memory and CPU usage before test execution: -.. image:: images/pap-s3p-top-before.JPG +.. image:: images/pap-s3p-mem-bt.PNG Memory and CPU usage after test execution: -.. image:: images/pap-s3p-top-after.JPG +.. image:: images/pap-s3p-mem-at.PNG -The CPU and memory usage by the PAP pod is consistent over the period of 72 hours test execution. Performance Test of PAP ++++++++++++++++++++++++ @@ -168,12 +168,12 @@ Test results are shown as below. **Test Statistics** -======================= ================= ================== ================================== ======================= -**Total # of requests** **Success %** **Error %** **Average time taken per request** **Requests/sec** -======================= ================= ================== ================================== ======================= -44293 100 % 0.00 % 943 ms 8858 -======================= ================= ================== ================================== ======================= +======================= ================= ================== ================================== +**Total # of requests** **Success %** **Error %** **Average time taken per request** +======================= ================= ================== ================================== +46314 100 % 0.00 % 1084 ms +======================= ================= ================== ================================== **JMeter Screenshot** -.. image:: images/pap-s3p-jm-performance.JPG
\ No newline at end of file +.. image:: images/pap-s3p-performance-result-jmeter.PNG
\ No newline at end of file |
