Creating a Roofline Analysis Task

Function

Roofline analysis helps pinpoint application bottlenecks on a given hardware platform and optimize the application accordingly.

Prerequisites

• No nodes are in the Offline state.
• The application to be analyzed must be a binary file in ELF format, and the application running user must have the read permission on the file.
• Only physical machines are supported.

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 roofline analysis task
   

   Table 1 Parameters for creating a roofline 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 Roofline.
   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	Only Application is supported.
   Mode	Only Launch application is supported.
   (Optional) Application User	Information about the OS user who runs the application. The application runs under the preset devkitworker1 user by default. If the application only runs under a specific user, enable the option, configure the corresponding user name and password, and then run the application.
   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.
   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. 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) must have the read and execute permissions on the applications to be analyzed.
   (Optional) Application Parameters	Set application parameters based on the actual scenario.
   Collection Mode	Select a mode for collecting application data. The options are total and region, and the default value is total. If you select region, check that you have completed region instrumentation for the application to be analyzed. For details about the instrumentation, see Roofline Instrumentation Guide. Otherwise, analysis data cannot be obtained.
   (Optional) Runtime Environment Variables	Environment variables required by the application. This parameter can be set in Advanced Configurations. NOTE: A maximum of 20 environment variables can be added.

3. Click OK.

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

   • : cancels the analysis task. After an analysis task is canceled, the collected information will be deleted.
   • : restarts the 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 the analysis task. After a task is deleted, all data of this task will be deleted. Exercise caution when performing this operation.
   • : creates a task for comparing analysis results.
   • : changes the task or report name. The report naming rule is the same as that of a task.