The scheduling jitter diagnosis feature analyzes issues that arise when a CPU does not switch tasks for an extended period, preventing user-mode applications from being scheduled. This can cause problems with memory reclamation. This topic describes how to use scheduling jitter diagnosis in the operating system console.
Limitations
Region
This feature is available only in the Chinese mainland and China (Hong Kong).
Permissions
If you use a RAM user, your Alibaba Cloud account (main account) must grant the
AliyunECSReadOnlyAccessandAliyunSysomFullAccesssystem policies to the RAM user.Operating system
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/3
CentOS 7.6 or later, or CentOS 8
Anolis OS 7/8
Ubuntu 24.04
ARM architecture
Alibaba Cloud Linux 3 Pro
Alibaba Cloud Linux 3
Procedure
Log on to the CloudMonitor 2.0 console, select the target workspace, and in the left-side navigation pane, click All Features.
On the All Features page, click CloudLens for ECS.
At the top of the page, click System Diagnosis (SysOM).
In the Diagnostic Mode section, select Node Diagnosis. From the Type of diagnosis list, select Scheduling diagnosis. From the Diagnostic Item list, select Scheduling jitter diagnosis. Configure the parameters and click Execute Diagnosis.
In the Diagnostic History section, click View Report.
Diagnostic report
Basic Information
The Basic Information section summarizes the diagnosis with key details, including the instance ID (which serves as the resource ID), diagnosis item, diagnostic report ID, and diagnosis start time.
Diagnostic conclusion
If scheduling jitter occurs, this section summarizes the detection results and details the causes of the jitter.
Diagnostic suggestions
This section provides recommended actions.
Diagnostic details
If scheduling jitter occurs, this section provides detailed information about the jitter.