Creating a Resource Scheduling Analysis Task

Function

The tool uses the eBPF technology to obtain metrics such as the cold flame graph, number of link switchovers, and global proportions. These metrics help to identify performance bottlenecks and analyze system calls of each process.

• You are advised to use an OS whose kernel version is 4.19 or later to run resource scheduling analysis tasks.
• BCC and Libbpf perform instrumentation of the kernel module with the root user permission and obtain process running data for analysis.

Prerequisites

No nodes are in the Offline state.

Procedure

1. Click next to System Profiler.

   Choose General Analysis from the drop-down list. The page for creating a task is displayed.

2. Set task parameters by referring to "Task Management" and Table 1.
   See Figure 1.

   Figure 1 Creating a resource scheduling analysis task
   

   Table 1 Parameters for creating a resource scheduling analysis task

   Parameter	Description
   Task Name	Name of the task. The name must meet the following requirements: Contain only letters, digits, and underscores (_). Contain 1 to 64 characters.
   Analysis Type	Select Resource Scheduling.
   Select Nodes	Select the nodes to be analyzed. If there is only one node, this node is selected by default. A maximum of 10 nodes can be selected at a time.
   Analysis Object	Select System or Application.
   Mode	Select Launch application or Attach to process. This parameter is mandatory when Analysis Object is set to Application.
   Application Path	Enter the absolute path of the application to be analyzed. For example, to analyze the loop_test application stored in the /home/test/ directory, enter /home/test/loop_test. Automatic path matching is supported. This parameter is mandatory when Analysis Object is set to Application and Mode is set to Launch application. NOTE: By default, applications in the /opt/ or /home/ directory are analyzed. The administrator can click in the upper right corner on the home page and choose Tool Settings > System Profiler > System Settings, and enter application paths (separated by semicolons) in the Application Path text box. Only administrators can modify this parameter. Common users can only view this parameter. You are advised to set the application path to a path such as /home or /opt. Do not set the application path to a system directory such as /, /dev, /sys, or /boot. Otherwise, system exceptions may occur. The OS running user (devkitworker1) of the System Profiler must have the read and execute permissions on the applications to be analyzed. In the multi-node scenario, you can enable Configure Node Parameters to configure this parameter separately for each node.
   (Optional) Application User	This parameter is available when Analysis Object is set to Application and Mode is set to Launch application. By default, this parameter is disabled. Disabled: The application running user is the default OS user devkitworker1. Enabled: The application running user is the configured user.
   Name	Name of the OS user who runs the application. This parameter is mandatory when Application User is enabled.
   Password	User password. This parameter is mandatory when Application User is enabled.
   PID	IDs of the process to be analyzed. One or more PIDs can be entered. You can click the text box or input a keyword of the process to be analyzed and then select the required PID. This parameter is mandatory when Analysis Object is set to Application and Mode is set to Attach to process. NOTE: If Attach to process is selected, the tool associates the ID of the process that runs an application to trace and collect the performance data of the application in real time. The OS running user devkitworker1 of the System Profiler must have the read permission on the application. To query the PID, run the ps -ef | grep Program_name command. You can enable Configure Node Parameters to configure this parameter separately for each node.
   Sampling Duration (s)	Sampling duration, in seconds. The default value is 60. The value range is 1 to 300. As the sampling duration increases, the collection processing may stop if the run directory space becomes insufficient. A maximum of 10 GB data can be collected. If the sampling duration is too long, a large number of resources and time will be consumed during collection and processing. Set this parameter properly.
   Sampling Delay (s)	The sampling starts after the specified time. This parameter is used to ignore the program startup analysis, warm up the sampling program, and eliminate sampling delay caused by factors such as environment detection. The default value is 0. The value range is 0 to 300. This parameter is mandatory when Analysis Object is set to Application and Mode is set to Launch application.
   Task Execution	The options are Execute now (default) and On a schedule. You need to set this parameter in Advanced Configurations. If On a schedule is selected, you need to set Sampling Mode, Sampling Time, and Sampling Date. For Periodical sampling mode, the task runs once a day in the sampling period. You need to set Sampling Time and Sampling Date. For One-Time sampling mode, the task takes effect only once. You need to set Sampling Date and Time. NOTE: A user can create a maximum of 20 scheduled tasks. You can click in the upper right corner of the page, choose Tool Settings > System Profiler, and click the Scheduled Tasks tab to view, edit, or delete (batch deletion supported) the created scheduled tasks. The Restart button is unavailable for scheduled tasks.

3. Click OK.

   You can click the icons next to the task name to perform the following operations:

   • : stops an analysis task. After an analysis task is stopped, the collected information will be deleted.
   • : restarts an analysis task. You can modify task parameter settings and restart an analysis task. This button is available when a task is canceled or fails.
   • : deletes an analysis task. After a task is deleted, all data of this task will be deleted. Exercise caution when performing this operation.
   • : performs analysis again. The analysis task is renamed and restarted.
   • : modifies the task or report name. The report naming rule is the same as that of a task.