Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Average processing time was calculated using last 10000 records from audit.log for each use case 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_performace_report.sh;h=846628543b5a127c49f57a1fa1f4a254dfff64da;hb=refs/heads/master

Result

Time taken by Drools PDP

...

Time taken by APP-C

Each In addition, each thread in the performance test script waits for notifications, via the POLICY-CL-MGT topic, to indicate that an APP-C request has been issued, and then injects the APP-C response via the REST interface.  Thus the elapsed time reported above includes time spent from the publish to POLICY-CL-MGT until the response is received on the REST interface.  This was calculated by examining all network.log files corresponding to the time when the test was executed 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_performace_report.sh;h=846628543b5a127c49f57a1fa1f4a254dfff64da;hb=refs/heads/master

Result

Time taken by Drools PDP

Use caseAverage time taken to execute one ONSET messageSample taken for average
vCPE341 msLast 10,000
vFirewall184 msLast 10,000
vDNS18 msLast 10,000
VOLTE16 msLast 10,000

Time taken by APP-C

Average time taken to publish request to POLICY-CL-MGT and receive response on REST interfaceSample taken for average
142 ms30,000

...