...
Performance test was triggered injecting vCPE, vFirewall, vDNS, VOLTE onset & abatement (where applicable) messages through REST interface of Drools PDP installed in windriver lab (PFPP). This was running on a kubernetes host, using the m2.xlarge spec, having the following configuration:
- 32GB RAM
- 8 VCPU
- 160GB Disk
The test environment was set-up using simulated components i.e. A&AI, VFC and SO using "features enable controlloop-utils". However the performance test subscribes to the POLICY-CL-MGT topic, which is not simulated, to determine when the PDP has completed various steps.
...
Average processing time was calculated using the last 10000 records from audit.log for each use case, as well as the matching transaction time extracted from the network.log, using the below script:
https://gerrit.onap.org/r/gitweb?p=policy/drools-applications.git;a=blob;f=testsuites/performance/src/main/resources/amsterdam/generate-mt-performance-report;h=846628543b5a127c49f57a1fa1f4a254dfff64da;hb=refs/heads/master
Result
Time taken by Drools PDP
| Code Block |
|---|
Elapsed time for vCPE : matched 8870 samples, average 18 ms unmatched 1130 samples, average 339 ms Elapsed time for vFirewall : matched 8871 samples, average 55 ms unmatched 1129 samples, average 177 ms Elapsed time for vDNS : matched 8869 samples, average 9 ms unmatched 1131 samples, average 16 ms Elapsed time for VOLTE : matched 8868 samples, average 9 ms unmatched 1132 samples, average 15 ms |
Note: the “unmatched samples” are requests for which no corresponding network time could be identified by the reporting tool. Hence those numbers represent the total elapsed time, with nothing subtracted out.
CPU Utilization
Total CPU used by the PDP was measured before and after the test, using "ps -l".
...