Several command combinations for viewing performance in the AIX System

Several command combinations for viewing performance in the AIX System
1) display 10 processes that consume the most CPU:
# Ps aux | head-1; PS aux | sort-rn + 2 | head-10
(2) display 10 processes that consume the most storage space:
# Ps aux | head-1; PS aux | sort-rn + 3 | head-10
(3) display the penalty processes in the system in sequence:
# Ps-EAKL | head-1; PS-EAKL | sort-rn + 5
(4) display processes in the system in priority order:
# Ps-EAKL | sort-N + 6 | HEAD
(5) display the first 10 processes in the system in the order of processing time:
# Ps VX | head-1; ps vx | grep-v pid | sort-rn + 3 | head-10
(6) display the first 10 processes in the system in the order of actual memory usage:
# Ps VX | head-1; ps vx | grep-v pid | sort-rn + 6 | head-10
(7) display the first 10 processes in the system in the order of the incoming pages:
# Ps VX | head-1; ps vx | grep-v pid | sort-rn + 4 | head-10
5. vmstat
The vmstat Command reports statistics on core threads, virtual memory, traps, disks, and CPU behavior. In addition, each behavior report is more detailed with percentages, indicating the user State, core State, idle and waiting for disk I/O.
Internal
The core maintains statistics on the Core Thread, page feed, and interrupt behavior, while the vmstat command accesses the data by using the knlist subroutine and the/dev/kmen pseudo device drive. Disk
The input/output statistics are maintained by the device drive. For disks, the average transmission speed is determined by the number of active time cores used to transmit information. The percentage of active time is when the drive is busy during the reporting period
Calculated from the inter-volume.
The vmstat command generates five types of reports:
· Inventory behavior reports
· Fork subprocess status report
· Interruption reports generated by each device
· Summary Report
· Input/output behavior report
6. SAR
The SAR Command reports CPU usage, I/O, and other system behaviors. SAR commands can collect, report, and save system behavior information. If no input file is specified, SAR calls the SARC command to access system data.
Use
Users can run the cron command to run two shell scripts (/usr/lib/SA/SA1 and/usr/lib/SA2) to provide daily statistics and reports. In the crontab file
/Var/spool/cron/crontabs/ADM contains sample sections to demonstrate when cron will run these shell scripts. Number collected in this way
It is useful for determining the time cycle characteristics of the system and determining the peak usage time.
Note that a considerable number of reads and writes are generated when the sar command is run by itself. Therefore, it is best to run SAR statistics without workload to see how much impact SAR has on the overall statistics.
7. topas
Topas
Commands are used to monitor various system resources, such as CPU usage, CPU events and queues, memory and paging space usage, disk performance, network performance, and NFS statistics. It also assigns reports to different
WLM processes consume system resources. It also reports hot categories of the most popular processes and Workload Manager (WLM) in the system. WLM class information is only displayed when WLM is activated.
The topas command defines popular processes as those that use a large amount of CPU time. The topas command does not have the log option, and all information is real-time.
Topas command Exploitation
System Performance Measurement interface (spmi) API to obtain relevant information. It is precisely because spmi
API to minimize system overhead. The topas command uses the perfstat library to call the perfstat kernel extension.
8. Truss
The truss command tracks system calls of a process, received signals, and machine errors. The application to be checked can be specified in the command line of the truss command, or the truss command can be mounted on one or more running processes.
AIX modulation Tool
1. fdpr
The fdpr command improves the execution time of user-level programs and libraries and the actual memory usage. The FDR command can be implemented through different operations, such as deleting unnecessary commands and reorganizing code and data. The FDR command is installed in the/usr/bin directory.
The fdpr command applies advanced optimization technology to the original code execution at three different stages to build an optimized executable code for it. The three phases are:
· In Phase 1, fdpr creates an executable program with some instruments added. The original executable program is saved as _ programfile. Save, and the new version is named _ programfile. instr.
· In Phase 2, fdpr runs an executable program that adds certain devices and collects Summary (profiling) data. The summary data is saved in a file named _ programfile. Prof. When running the program, you need to provide it with typical input data so that the fdpr command can identify the optimizable part of the code.
· In Phase 3, The fdpr Command Re-sorts executable code using the important information collected in Phase 2. The sorting involves the following tasks:
(1) package the high-frequency Execution Code sequences together.
(2) re-order the parts of the condition to improve the hardware's prediction of the points of the condition.
(3) Remove less-used code.
(4) embedded some popular functions.
(5) Delete the Nop (null operation) command from the re-ordered code.
In addition, the compiler also provides a-qfdpr flag that allows the compiler to add additional information in the code to assist fdpr in re-sorting the executed code. However, if this-qfdpr flag is used, fdpr only sorts those modules compiled with the-qfdpr flag again.
2. schedtune
The schedtune command can set guidelines for jitter, process suspension, time slice, and the length of time that a thread can poll when it is locked.
Use
Schedtune, which can be used to adjust a set of parameters in Aix that affect its memory load control mechanism. The schedtune command is used to display and modify those used to detect excessive system memory usage.
Used to cause jitter. The schedtune command can also be used to modify the penalty and attenuation factors of processes running on the system. Run the schedtune command as the root user.
Things:
· Determine the criteria used to determine jitter.