|
|||
1. Managing Terminals and Modems (Overview) 2. Setting Up Terminals and Modems (Tasks) 3. Managing Serial Ports With the Service Access Facility (Tasks) 4. Managing System Resources (Overview) 5. Displaying and Changing System Information (Tasks) 8. Scheduling System Tasks (Tasks) 9. Managing System Accounting (Tasks) 10. System Accounting (Reference) 11. Managing System Performance (Overview) Where to Find System Performance Tasks System Performance and System Resources Processes and System Performance About Monitoring System Performance 12. Managing System Processes (Tasks) 13. Monitoring System Performance (Tasks) 14. Troubleshooting Software Problems (Overview) 16. Managing Core Files (Tasks) 17. Managing System Crash Information (Tasks) 18. Troubleshooting Miscellaneous Software Problems (Tasks) 19. Troubleshooting File Access Problems (Tasks) 20. Resolving UFS File System Inconsistencies (Tasks) |
What's New in Managing System Performance?This section describes new or changed features in managing system performance in the Solaris release. Enhanced pfiles ToolSolaris 10: The /proc file system has been enhanced to include file name information in the /proc/pic/path directory. This information is used by pfiles to display file names for each file in the process. This change provides new insight into process behavior. For more information, see How to Display Information About Processes and the proc(1) man page. CPU Performance CountersSolaris 10: The CPU Performance Counter (CPC) system has been updated to give better access to the performance analysis features available in the SPARC and x86 platforms that run the Solaris Operating System. The CPC commands cpustat and cputrack have enhanced, command-line syntax for specifying CPU information. For example, in previous versions of the Solaris OS, you were required to specify two counters. The configuration of both commands now allows you to specify only one counter, as shown in the following example: # cputrack -c pic0=Cycle_cnt ls -d . time lwp event pic0 pic1 . 0.034 1 exit 841167 For simple measurements, you can even omit the counter configuration, as shown in the following example: # cputrack -c Cycle_cnt ls -d . time lwp event pic0 pic1 . 0.016 1 exit 850736 For more information on using the cpustat command, see the cpustat(1M) man page. For more information on using the cputrack command, see the cputrack(1) man page. |
||
|