검색

Chapter 3. Resource optimization for OpenShift optimization reports

download PDF

Access resource optimization for OpenShift from the Red Hat Hybrid Cloud Console to see detailed recommendations for how to optimize your Red Hat OpenShift clusters.

3.1. Enabling optimization

To receive resource optimization recommendations for your namespaces, you must first enable each namespace. To enable a namespace, label it with insights_cost_management_optimizations='true'.

In the CLI, run: oc label namespace NAMESPACE insights_cost_management_optimizations="true" --overwrite=true

3.2. Viewing optimization reports

Prerequisites

Procedure

  1. In cost management, click the tab Optimizations.
  2. Search for an optimization or use the filter. Click the link to the optimization that you selected.
  3. View details about the recommendation and toggle between Cost optimizations and Performance optimizations. For more information, see Optimizing for cost or for performance.

3.3. Optimizing for cost or for performance

After you select an optimization, you can toggle between two tabs called Cost optimizations and Performance optimizations. Optimizing for cost uses less resources and is useful when you are performing tests where there is no impact to users. Optimizing for performance provides all the resources possible and is helpful for apps running in a production cluster.

In Cost optimizations, recommendations get generated when CPU usage is at or above the 60th percentile and memory usage is at the 100th percentile. In Performance optimizations, recommendations get generated when CPU usage is at or above the 98th percentile and when memory usage is at the 100th percentile.

3.4. Understanding box plots

On the Optimizations page, there are two box plots for your Current CPU utilization and your Current memory utilization. These visualizations can help you understand resource distribution and identify outliers in your data. You can export the data in CSV and JSON format.

The box plots display the following data points in millicpu (m) for CPU and in mebibytes (Mi) for memory:

  • Minimum
  • Maximum
  • Median
  • First quartile (Q1): value where 25% of data points are when they are arranged in increasing order
  • Third quartile (Q3): value where 75% of data points are when they are arranged in increasing order
  • Recommended limit
  • Recommended request

The data points are based on the time period that you selected:

  • 1 day = 4 data points
  • 7 days = 7 data points
  • 14 days = 14 data points
Red Hat logoGithubRedditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

© 2024 Red Hat, Inc.