Performance Testing is a form a testing that focus on how a system runs under a particular load. Though we can asses the system by different performance metrics, the initial analysis will focus on the load testing of APPC.
For Dublin release APPC will meet Level 2 Performance requirements as described at Performance
Load Test:
APPC LCM can be invoked in two ways,
- DMAAP
- APPC API
For this load test we will use APPC API to analyse the performance of the system to minimize the external systems influence on APPC.
Assumptions:
APPC interacts with other external systems such as A&AI & AAF. This analysis will not test the APPC independently rather it will test it along with its dependents so there may occur an error correction due to network bandwidth or dependent system availability.
The other system APPC dependent on is VNF. For this testing we use Mock VNF (Dummy VNF). This requires doing the installation of the VNF package in Windriver lab.
The code for Mock VNF is at Mock VNF. This VNF supports only NETCONF Protocol and all the Performance testing is done for NETCONF-XML.
The next plan will include ANSIBLE & CHEF Protocol testing.
Tools Used:
This testing process will use Jmeter to create concurrent request and increase the load on APPC gradually.
...
Footprint of docker images:
| Image | Size |
|---|---|
| onap/appc-image | 2.88GB |
| onap/appc-cdt-image | 160MB |
| onap/ccsdk-odlsli-image | 1.81GB |
| mariadb 10.1.11 | 346MB |
| Total | ~5.2GB |
Performance measurements baseline
APPC performance measurement baseline should include values for common daily tasks that are executed for VNFs.
e.g. ConfigModify, audit, healthcheck, start/stop VNF etc.
Example of execution times for common APPC operations:
| Operation | Average Time (ms) |
|---|---|
| Query | 14049 |
| Start | 14739 |
| Stop | 14512 |
| Snapshot | 12299 |
| Restart | 15907 |
An example of metric log entries:
...