blob: bc8b79b3a36ac0cb0b1f922f2b5ce5e8ff942f83 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
|
.. This work is licensed under a
.. Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. _drools-s3p-label:
.. toctree::
:maxdepth: 2
Policy Drools PDP component
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Both the Performance and the Stability tests were executed against an ONAP installation in the Policy tenant
in the UNH lab, from the admin VM running the jmeter tool to inject the load.
General Setup
*************
Agent VMs in this lab have the following configuration:
- 16GB RAM
- 8 VCPU
Jmeter is run from the admin VM.
The drools-pdp container uses the JVM memory and CPU settings from the default OOM installation.
Other ONAP components exercised during the stability tests were:
- Policy XACML PDP to process guard queries for each transaction.
- DMaaP to carry PDP-D and jmeter initiated traffic to complete transactions.
- Policy API to create (and delete at the end of the tests) policies for each
scenario under test.
- Policy PAP to deploy (and undeploy at the end of the tests) policies for each scenario under test.
- XACML PDP Stability test was running at the same time.
The following components are simulated during the tests.
- SDNR.
Stability Test of Policy PDP-D
******************************
PDP-D performance
=================
The tests focused on the following use cases running in parallel:
- vCPE
- SON O1
- SON A1
Three threads ran in parallel, one for each scenario. The transactions were initiated
by each jmeter thread group. Each thread initiated a transaction, monitored the transaction, and
started the next one 250 ms. later.
The results are illustrated on the following graphs:
.. image:: images/s3p-drools-1.png
.. image:: images/s3p-drools-2.png
.. image:: images/s3p-drools-3.png
Commentary
==========
There is around 1% unexpected failures during the 72-hour run. This can also be seen in the
final output of jmeter:
.. code-block:: bash
summary = 4751546 in 72:00:37 = 18.3/s Avg: 150 Min: 0 Max: 15087 Err: 47891 (1.01%)
Sporadic database errors have been observed and seem related to the 1% failure percentage rate.
|
