Feature Overview

Performance is a variable that can be tuned based on how a product is used. Ideally, with Openshift Kernel Isolated Containers performance should be as close as possible to native. To understand how to optimize a system to achieve optimal performance, one must perform a sensitivity-analysis, this way it is easy to interpret and make informed decisions about system configuration to achieve the best-desired performance outcomes.

Background, and strategic fit

Customers for Openshift Sandboxed Containers are coming from different verticals and backgrounds. They also have different use-cases. Understanding how the system behaves in terms of performance for each use-case is key to picking the right configuration defaults that would lead to best performance results for each use-case.

Goal(s)

The goal is to do a sensitivity-analysis for:

• Network Performance Trade-offs (e.g., with and without SR-IOV)
• Storage I/O performance
• Compute performance

Also one of the main goals is to understand the trade-offs between a default runtime such as runC and Kata. Understand the trade-offs will help users decide when it makes sense to use one over the other.

Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?
• Does this feature have doc impact?
• New Content, Updates to existing content, Release Note, or No Doc Impact
• If unsure and no Technical Writer is available, please contact Content Strategy.
• What concepts do customers need to understand to be successful in [action]?
• How do we expect customers will use the feature? For what purpose(s)?
• What reference material might a customer want/need to complete [action]?
• Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or Release Note)?