Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Platform Maturity - Performance Level 1

Description

As OOF developer I would like to support the Performance Platform Maturity Requirement for the Beijing release. The target level for OOF in Beijing release is Level 1.

This requires that the baseline performance criteria is identified and measured (such as response time, transaction/message rate, latency, footprint, etc. to be defined on per component)

-----------

From a platform standpoint this involves the following

  • Work with the OOM team to understand the impact of Kubernetes performance on application performance 

  • Work with the logging team to understand the impact of logging performance on application performance

  • Use performance as one of the key metrics in OOF database selection (for example, a no-sql database can deliver the same functionality as a graph database with much better performance)

Activity

Show:

Former user May 15, 2018 at 7:47 PM

In R2, the following baseline performance metrics are measured, and are logged or persisted in DB based on the metric :

  • Time spent in each phase of the plan lifecycle Lifecycle. This metric is persisted in Music.

  • Configuration driven timeout for a homing request (ensures monotonicity of a homing task to completion).

  • Intra-component messaging: Time taken for each message between the various homing components. This metric is logged.

  • Communication with other dependencies: Time taken for the calls to inventory (AAI) and VIM (MultiCloud) for data retrieval. This metric is logged.

Done

Details

Assignee

Reporter

Fix versions

Priority

Parent

Created January 8, 2018 at 11:07 PM
Updated August 12, 2023 at 4:21 AM
Resolved May 15, 2018 at 7:47 PM