Creating a Tuning Analysis Task

Function

The Tuning Assistant systematically organizes and analyzes performance metrics, hotspot functions, and system configurations to form a system resource consumption chain. It provides guidance for analyzing performance bottlenecks based on tuning paths and gives tuning suggestions and operation guides for each tuning path to implement fast tuning.

Prerequisites

No nodes are in the Offline state.

Procedure

1. Click next to Tuning Assistant.

   Click Create Tuning Analysis. The New TunAssist_Tuning Task page is displayed.

2. The content on the page varies according to the analysis object and mode. Table 1 describes the task parameters.

   Create a tuning analysis task. See Figure 1.

   Figure 1 Creating an analysis task
   

   Table 1 Parameters for creating a tuning analysis task

   Parameter	Description
   Task Name	By default, a task name is generated in the format of TuningAssistant_TaskN. You can modify the task name as required. Name of the analysis task. The name must meet the following requirements: N is an integer starting from 1 in ascending order. The name can contain 1 to 64 characters, including letters, digits, and underscores (_).
   Select Nodes	Nodes to be analyzed. By default, only one node is selected. A maximum of 10 nodes can be selected.
   Analysis Object	Object to be analyzed. The options are: System: Collects performance data of the server, regardless of the types of applications running in the system. The sampling duration is determined by the parameter specified. This option is recommended for servers running multiple types of services and subprocesses. Application: Collects data of a specified application or process for analysis.
   Mode	Mode for application analysis. The options are: Launch application: Starts the application when the sampling begins. The sampling duration is determined by the execution time of the application. This option is recommended for applications with short execution time. The analysis covers the application and its subprocesses. Attach to process: associates the existing PIDs on the server during data collection. You need to configure the sampling duration parameter (applicable to scenarios where the application runs for a long time). The analysis covers only the PIDs in the parameter, not the sub-processes of the PIDs.
   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.
   (Optional) Application Parameters	Set application parameters based on the actual scenario.
   Application User	This parameter is disabled by default. Disabled: The application running user is the default OS user devkitworker1. Enabled: The application running user is the configured user.
   Process	Name of the process to be analyzed. Regular expressions are supported.
   PID	ID of the process to be analyzed. Separate multiple PIDs with commas (,).
   Symbol File Path	Absolute path of the symbol file on the server. NOTE: You can use this parameter to import the symbol table of an application when you need to view the performance data after source code and assembly instructions are mapped but the corresponding application has no symbol table information. If the binary file of the application contains debug information, you only need to save the binary file in the directory. If the binary file of the application does not contain debug information, save the binary file and the corresponding debug information file in the directory.
   Sampling Duration (s)	Sampling duration, in seconds. The default value is 15. The value range is 2 to 300.
   Size of the Collected File (MiB)	Size of the collected file. The default value is 100. The value ranges from 1 to 100.

3. Click Start Now. In the confirmation dialog box that is displayed, click OK.

   You can click the icon next to the task name or node name to perform the following operations:

   • : modifies the task parameters and performs an analysis again.
   • : views the analysis path of a task or node.
   • : views basic task information and logs.
   • : deletes an analysis task. After a task is deleted, all data of this task will be deleted. Exercise caution when performing this operation.
   • : cancels an ongoing analysis task.
   • : modifies a task or report name.
   • : creates a task for comparing analysis results.
   

   • The administrator devadmin can view, modify, and delete the analysis tasks of all users. Common users can view, repeat, and delete their own analysis tasks and view tasks created by other users.
   • If the name of a repeated analysis task is the same as that specified during task creation, the repeated task cannot be started.
   • When changing the task or report name, ensure that the new name meets the following requirements:
     • Contain 1 to 64 characters, including letters, digits, and underscores (_).