Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Summary

Stability test plan was triggered for 72 hours injecting vCPE, vFirewall, vDNS, VOLTE onset & abatement (where applicable) messages through REST interface of Drools PDP installed in windriver lab (PFPP).

The test environment was set-up using simulated components i.e. A&AI, VFC and SO using "features enable controlloop-utils".

APPC response messages were injected in test plan wherever needed.

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/stability/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
vCPE3 msLast 10,000
vFirewall2 msLast 10,000
vDNS8 msLast 10,000
VOLTE7 msLast 10,000


CPU Utilization

Average:        CPU     %user     %nice   %system   %iowait    %steal     %idle
Average:        all      0.84      0.00      0.23      0.02      0.00     98.91
Average:          0      1.16      0.00      0.30      0.00      0.00     98.54
Average:          1      1.00      0.00      0.25      0.00      0.00     98.75
Average:          2      1.21      0.00      0.33      0.00      0.00     98.46
Average:          3      0.78      0.00      0.18      0.00      0.00     99.03
Average:          4      0.77      0.00      0.18      0.00      0.00     99.04
Average:          5      0.80      0.00      0.28      0.12      0.00     98.80
Average:          6      0.54      0.00      0.13      0.00      0.00     99.33
Average:          7      0.49      0.00      0.14      0.00      0.00     99.37


Memory Utilization

Number of young garbage collection: 6711
Avg. Young garbage collection time: ~7.09 ms per collection
Number of Full garbage collection: 4
Avg. Full garbage collection time: ~197 ms per collection

 S0     S1     E      O      M     CCS    YGC     YGCT    FGC    FGCT     GCT  
0.00  90.62  45.71  21.36  97.74  93.42   6711   47.578     4    0.788   48.366 


Performance Metrics

No.

Metric

Description

ResultComments
1Single Threaded Response TimeMeasure the execution time for onset and abatement in each use case with only a single policy executing

vCPE - 3 ms

vFirewall - 2 ms

vDNS - 8 ms

VOLTE - 7 ms

The average time taken is calculated based on last 10,000 samples in audit.log file.
2Single Threaded CPU UsageCPU Usage for each use case when executing alone~ 1%
3Single Threaded Memory UsageMemory Usage for each use case when executing alone~ 100 MB
4Maximum Simultaneous ExecutionsMeasure the maximum number of simultaneous policy executions that can be achieved whilst maintaining system stability and resource utilization2The current size of source/sink topics is 10. And 1 onset message results to 5 messages in sink topic. Hence we can only run 2 simaltaneous thread and assert the values coming in sink topics.
  • No labels