CPU Utilization

Procedure

  1. Check the system version.
  2. Check the service pressure.

    • If the system version is V100R002C00SPC010, V100R002C00SPC011, V100R002C00SPC012, V100R002C00SPC013, V100R002C00SPC014, V100R002C01SPC007, V100R002C01SPC011, V100R002C01SPC012, or V100R002C01SPC013 => Consult with the customer to determine whether the current service pressure is heavy.
    • If the system is in V100R002C00SPC015, V100R002C01SPC015, V100R005C00SPC003, or any of their later versions => see 3 to enter the minisystem mode. Run the iostat -xdtk 1 10 command to check the workload of service disks.

      %util indicates disk utilization. A larger value indicates a higher I/O pressure.

    • If the system is in any of V100R001 versions, versions earlier than V100R002C00SPC010 or V100R002C01SPC007 => see 4 to enter the debug mode. Run the iostat -xdtk 1 10 command to check the workload of service disks.

      The command output in debug mode is the same as that in minisystem mode, so the screenshot is not provided here.

    If the service pressure is too heavy, do not perform the check until the pressure is small.

    • The check is passed => No further action is required.
    • The check is failed =>
      • If the system is in V100R002C00SPC015, V100R002C01SPC015, V100R005C00SPC003, or any of their later versions => 3.
      • If the system is in any of V100R001 versions, versions earlier than V100R002C00SPC010 or V100R002C01SPC007 => 4.
      • If the system version is V100R002C00SPC010, V100R002C00SPC011, V100R002C00SPC012, V100R002C00SPC013, V100R002C00SPC014, V100R002C01SPC007, V100R002C01SPC011, V100R002C01SPC012, or V100R002C01SPC013 => 5.

  3. Enter the minisystem mode and check processes that occupy a large number of CPU resources. If the processes are os_debug_mode*, stop the processes.
    1. Log in to disk arrays as user admin.

    2. Run the developer command, input the debugging password (debug@storage) to enter the developer mode.

    3. Run the minisystem command to enter the minisystem mode.

    4. Run the top command to check processes that occupy a large number of CPU resources.

      %CPU indicates the CPU usage. By default, the process in the first line occupies the most CPU resources. Normally, the process in the first line is os_debug_mode*.

    5. Run kill -9 process pid to stop the os_debug_mode* process.

      Obtain the process pid from the PID column in the figure above.

  4. Enter the debug mode and check processes that occupy a large number of CPU resources. If the processes are os_debug_mode*, stop the processes.
    1. Log in to disk arrays as user admin.
    2. Run the developer command, input the debugging password to enter the developer mode.

      For the method of obtaining the debug password, see Obtaining the Debug Password.

    3. Run debug command to enter the debug mode.

      NOTICE:

      In V100R001, the debug password is the same as the developer password.

    4. Run the top command to check processes that occupy a large number of CPU resources.

      %CPU indicates the CPU usage. By default, the process in the first line occupies the most CPU resources. Normally, the process in the first line is os_debug_mode*.

    5. Run kill -9 process pid to stop the os_debug_mode* process.

      Obtain the process pid from the PID column in the figure above.

  5. If you have any questions, please contact technical support engineers for further handling.
Parent topic: System