Pamela Dragosh | ba45dc6 | 2020-04-16 09:27:44 -0400 | [diff] [blame] | 1 | .. This work is licensed under a |
| 2 | .. Creative Commons Attribution 4.0 International License. |
| 3 | .. http://creativecommons.org/licenses/by/4.0 |
| 4 | |
| 5 | .. _xacml-s3p-label: |
| 6 | |
| 7 | .. toctree:: |
| 8 | :maxdepth: 2 |
| 9 | |
| 10 | Policy XACML PDP component |
| 11 | ~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 12 | |
| 13 | Performance Test of Policy XACML PDP |
| 14 | ++++++++++++++++++++++++++++++++++++ |
| 15 | |
| 16 | Summary |
| 17 | ------- |
| 18 | |
| 19 | The Performance test was executed by performing requests against the Policy RESTful APIs residing on the XACML PDP installed in the windriver lab to get policy decisions for monitoring and guard policy types. This was running on a kubernetes host having the following configuration: |
| 20 | |
| 21 | - 16GB RAM |
| 22 | - 8 VCPU |
| 23 | - 160GB Disk |
| 24 | |
| 25 | The performance test runs 10 simultaneous threads calling XACML PDP RESTful APIs to get decisions for Monitoring, Guard Min Max, and Guard Frequency Limiter policy types, with at duration of 6000 seconds. The test execution lasted approximately 50 minutes resulting in the following summary: |
| 26 | |
| 27 | - 37,305 Healthcheck requests |
| 28 | - 33,716 Statistics requests |
| 29 | - 25,294 Monitoring decision requests |
| 30 | - 25,288 Guard Min Max decisions |
| 31 | - 25,286 Guard Frequency Limiter requests |
| 32 | |
| 33 | The average throughput was about 9.8 transactions per second. CPU and memory usage along with a screenshot of the JMeter Summary Report are provided in this document. |
| 34 | |
| 35 | Results |
| 36 | ------- |
| 37 | |
| 38 | **CPU Utilization** |
| 39 | |
| 40 | Total CPU used by the PDP was measured before and after the test, using "ps -l". |
| 41 | |
| 42 | =================== ================== ================ =================== =============== ================== |
| 43 | **Intial CPU time** **Final CPU time** **Intial CPU %** **Intial Memory %** **Final CPU %** **Final Memory %** |
| 44 | =================== ================== ================ =================== =============== ================== |
| 45 | 00:60:27 00:73:45 3.5% 4.0% 94.12.3% 4.0% |
| 46 | =================== ================== ================ =================== =============== ================== |
| 47 | |
| 48 | **Memory Utilization** |
| 49 | |
| 50 | .. code-block:: bash |
| 51 | |
| 52 | Number of young garbage collections used during the test: 518 |
| 53 | Avg. Young garbage collection time: ~11.56ms per collection |
| 54 | Total number of Full garbage collection: 32 |
| 55 | Avg. Full garbage collection time: ~315.06ms per collection |
| 56 | |
| 57 | |
| 58 | S0C S1C S0U S1U EC EU OC OU MC MU CCSC CCSU YGC YGCT FGC FGCT GCT |
| 59 | |
| 60 | 16768.0 16768.0 0.0 5461.0 134144.0 71223.6 334692.0 138734.5 50008.0 48955.8 5760.0 5434.3 4043 45.793 32 10.082 55.875 |
| 61 | |
| 62 | 16768.0 16768.0 0.0 4993.4 134144.0 66115.7 334692.0 252887.4 50264.0 49036.5 5760.0 5439.7 4561 53.686 32 10.082 63.768 |
| 63 | |
| 64 | **Jmeter Results Summary** |
| 65 | |
| 66 | .. image:: images/xacml-s3p.PNG |