The scheduling jitter diagnosis feature analyzes issues where prolonged CPU task-switching delays, such as during memory reclamation, prevent user-mode business processes from being scheduled. This topic describes how to use the scheduling jitter diagnosis feature in the OS management console.
Limitations
Region support
This feature is currently available only in the Chinese mainland and Hong Kong (China) regions.
Operating system support
Architecture
Operating system
x86 architecture
Rocky Linux 9.5
Rocky Linux 9.1
Ubuntu 20.04
Alibaba Cloud Linux 3 Container-Optimized Edition
Rocky Linux 8.8
Ubuntu 22.04
Alibaba Cloud Linux 3 Pro
Alibaba Cloud Linux 2 and 3
CentOS 7.6 or later, or CentOS 8
Anolis OS 7 and 8
Ubuntu 24.04
Arm architecture
Alibaba Cloud Linux 3 Pro
Alibaba Cloud Linux 3
Prerequisites
If you use a RAM user, ensure the root account has granted the
AliyunECSReadOnlyAccessandAliyunSysomFullAccesssystem policies to the RAM user.The OS management console service is enabled.
When you log in to the OS management console for the first time, click Enable Service.
Procedure
Go to the OS management console.
In the left-side navigation pane, click System Diagnosis.
In the upper-left corner of the page, select the region of your target instance.
From the Diagnosis Type list, select Scheduling Diagnosis. From the Diagnostic Item list, select Scheduling Jitter Diagnosis. Configure the parameters and click Run Diagnosis.
NoteIf SysOM is not installed on the target ECS instance, the system automatically installs it and starts the diagnosis after you click Run Diagnosis.
The following table describes the parameters.
Parameter
Description
Instance ID
The ID of the target ECS instance.
Diagnosis duration
The duration of the real-time diagnosis. The default value is 20 seconds.
Jitter threshold
The threshold for identifying scheduling jitter. The default value is 20 ms.
In the Diagnosis Record section, click View Report.
Diagnosis report
Basic information
This section contains basic information about the diagnosis, including the instance ID (resource ID), diagnostic item, diagnosis report ID, and the time the diagnosis started.
Diagnostic conclusion
If scheduling jitter is detected, this section summarizes the findings and details the causes of the jitter.
Diagnostic suggestion
This section offers recommendations based on the diagnostic findings.
Diagnostic details
If scheduling jitter is detected, this section records detailed information about the jitter.