AHF Release 24.11

Parent topic: 2024 AHF Releases

Optimize Database Performance and Hardware Usage

AHF Balance now allows limiting the number of databases included in performance tuning recommendations. This makes it easier to implement gradual configuration changes to enhance performance without overwhelming change management processes.

AI-Driven Tuning with AHF Balance

AHF Balance uses AI to provide tuning recommendations for database CPU_COUNT. Database Administrators (DBAs), Cluster Administrators, and Fleet Administrators can leverage these recommendations to optimize database performance while maximizing hardware utilization.

Enhanced Flexibility for Tuning Recommendations

Previously, AHF Balance considered all databases within a cluster as candidates for CPU_COUNT adjustments. This often led to recommendations for modifying CPU_COUNT on 50 or more databases, posing challenges for implementing such extensive changes simultaneously.

With the new --limit-db-changes option, AHF Balance enables incremental performance improvement by capping the number of databases included in tuning recommendations. This allows administrators to make changes in manageable stages through successive iterations of tuning.

Note:

Before running the ahf analysis command with the --type impact option, ensure that you first run the configuration command: ahf configuration set --type impact --user-name USER_NAME --connect-string CONNECT-STRING

This step is necessary to set up the required connection details before performing the analysis.

Command Usage Examples
  • Fleet Analysis:
    To perform an analysis for a fleet and limit the number of database changes across clusters, use:
    ahf analysis create --type impact --scope fleet --name <fleet-name> --limit-db-changes <positive-integer-number-of-databases>
  • Cluster Analysis:
    To perform an analysis for a specific cluster and limit the number of database changes, use:
    ahf analysis create --type impact --scope cluster --name <cluster-name> --limit-db-changes <positive-integer-number-of-databases>
  • Database Analysis within a Cluster:
    To perform an analysis for a specific database within a cluster, use:
    ahf analysis create --type impact --scope database --name <db-name> --cluster <cluster-name> --limit-db-changes <positive-integer-number-of-databases>

By limiting database changes, AHF Balance provides a more controlled and efficient approach to performance tuning, ensuring smoother implementation and improved results.

Related Topics

Parent topic: AHF Release 24.11

New Oracle Orachk and Oracle Exachk Best Practice Checks

Release 24.11 includes the following new Oracle Orachk and Oracle Exachk best practice checks.

Best Practice Checks Common to Both Oracle Orachk and Oracle Exachk

Oracle Orachk Specific Best Practice Checks

  • Verify systemd-udevd process CPU usage

Oracle Exachk Specific Best Practice Checks

All checks can be explored in more detail via the Health Check Catalogs:

Related Topics

Parent topic: AHF Release 24.11