Page Comparison

The Platform Maturity requirements for Beijing Casablanca are on this page:
Platform Maturity Requirements (aka Carrier Grade)Casablanca Release Requirements

The ambition for the ONPA ONAP Policy Framework is to reach level 1 2 in performance in Beijing, see JIRA POLICY-392Casablanca, see

For Performance Level 1, we have had to define and measure our performance metrics:
Level 1: baseline performance criteria identified and measured  (such as response time, transaction/message rate, latency, footprint, etc. to be defined on per componentI don't think we have to state what the metrics should be, it looks like we just define the metrics and measure them. For

Measurements were taken in the Beijing release for the Single-Threaded case.  Additional measurements are to be taken in the Casablanca release, for the Multi-Threaded case (i.e., multiple threads, each generating their own ONSET events).

Depending on the results, for Level 2, an improvement plan must be created and implemented.

Although there should be measurements for design time and deployment time performance, here we continue to focus on the run time performance metrics for policy execution in the PDPs, the most critical run time metrics for Policy. We propose to measure these metrics in a simulated environment and in a full ONAP deployment.

Measurements for the "Single Threaded" case are were made in Beijing using the Stability test, which uses timers to determine when to inject responses via REST.  It also uses the REST API to look for "FINAL" states, thus it is limited to two threads.  On the other hand, the measurements for the "Multi Threaded" case are made using the Performance test, which uses DMaaP notifications to determine when to inject responses via REST.  It also uses DMaaP notifications to look for "FINAL" states, thus it is only limited by how many simultaneous consumers and connections are supported by DMaaP.

...