W517 Monitoring Array System Performance

Transcription

1 W517 Monitoring Array System Performance Pre-requisites: None Designed for the Array system administrator, this session will center around troubleshooting system performance. Topics covered will be recommended purges, reorganization of data, system backup schedules, and much more. If you're looking to hone your system performance, you won't want to miss this session. Scott Arble Technical Support Wednesday, 2:30 p.m. 2 Session Objectives Discuss tools to monitor system performance Understand the three areas of bottlenecks Checking Array databases

2 3 Return on Investment Opportunity A machine that can keep up with your employees will help keep the employees productive and happy Machines that under-perform cause employee frustration and loss of productivity may affect the bottom line 4 Bottlenecks Memory low memory may cause: Sluggish performance Fork Function Failed message Screens that hesitate when painting Disk I/O Balance load of read / writes to multiple disks CPU A CPU bound system would have problems with reports running including DAYEND reports

3 5 AIX Tools to Monitor Performance iostat Monitors disk activity vmstat Monitors memory usage topas AIX tool to monitor system performance in many areas at one time filemon Monitor file access 6 iostat Shows CPU and disk iostat - will show activity since reboot iostat will display current stats at 3 second intervals 5 times

4 7 iostat Make sure disk activity is balanced Check CPU stats when disk activity is high 8 iostat

5 9 vmstat Shows memory statistics and CPU usage vmstat run by itself will stats since last system reboot vmstat 3 5 will show current stats at 3 second intervals 5 times 10 vmstat Watch for free memory getting too low Watch for values under PI and PO columns which may indicate a memory issue

6 11 vmstat 12 topas Shows stats on areas of system performance on one screen Available in AIX 5.x Must be logged on as root to use Type the command topas to get started

7 13 topas 14 filemon Monitors file usage filemon o fmon.out O all The above command will create an output file fmon.out that can viewed to show the following information Most active files Most active logical volumes Most active physical disks

8 15 Performance Diagnostic Tool (PDT) Collects configuration and performance information and attempts to identify potential problems /usr/sbin/perf/diag_tool/pdt_config Enables collection of data Entries are made in the adm cron to collection information Reports can be ed to users 16 Performance Diagnostic Tool (PDT) Monitors I/O configuration Paging configuration Processes File Systems Files

9 17 Performance Diagnostic Tool (PDT) Thresholds can be defined in /var/perf/cfg/diag_tool/.thresholds Ping delays to different hosts can be tracked by creating the /var/perf/cfg/diag_tool/.nodes file Report can be generated at any time using the command /usr/sbin/perf/diag_tool/pdt_report 18 dcheck Cobol utility to check the integrity of a database and the number of records in a database Must be logged on prog dcheck /data13/live/wipd00

10 19 dcheck 20 Purges Create and verify a good backup prior to running any purge Array has purges created to delete records after a period of time Purges must be run manually Purge deletes the records Files must be restored from backup if too much information is purged Recommend purges to be run monthly

11 21 ONESTP Create and verify a backup before running any ONESTP programs Utility used to rebuild a database Clean up indices Speed up access to the database Do not need to be run after each purge Should be run if large amounts of data are being deleted from the system Consists of four steps 22 ONESTP Step 1 *** DCHECK *** START TIME: 00:37:03:25 TOTAL REC INPUT TOTAL REC OUTPUT TOTAL REC DELETED END TIME: 00:41:21:00

12 23 ONESTP Step 2 *** REORGO *** START TIME: 00:41:21:04 TOTAL REC INPUT TOTAL REC OUTPUT END TIME: 00:42:26:99 24 ONESTP Step 3 *** NEWDBS *** SUCCESSFUL INITIALIZING OR UNSUCCESSFUL INITIALIZING - FILE IS CURRENTLY OPEN *** ERROR ***

13 25 ONESTP Step 4 *** REORGI *** START TIME: 00:42:27:41 TOTAL REC INPUT TOTAL REC OUTPUT END TIME: 00:50:21:47 26 TURBO Array utility to increase system performance for long running reports and nightly jobstreams For example some customers have seen a decrease from 6 hours of nightly processing down to 2 hours with Turbo deployed This is a custom program and there is a charge for this program Try and Buy available for TURBO

14 27 uptime Utility to show quick status of last system Shows last reboot Number of users logged on to system CPU usage in last 5, 10, 15 minutes 28 uptime

15 29 ps aux The command ps aux will list all the processes running on the system in order of priority ps aux ps aux head 20 will show top 20 processes 30 ps aux

16 31 lsps The command lsps will list paging space usage on the system Low paging space may cause Fork Function Failed errors and extreme slowness on the system lsps s will give a summary on paging space lsps a will show detail about each memory area 32 lsps

17 33 Suggested Action Plan Performance should be monitored when the system is running correctly Once the baseline is established, comparisons can be made when system performance has been degraded 34 Summary Create a baseline when the system is running smoothly to use as a benchmark when the system has performance problems Use the tools to help determine where the problem exists Keep up on purges in the Array software

18 35 Thank You for Attending W517 Monitoring Array System Performance Scott Arble Please submit the Session Feedback Form To receive NASBA credits, please be sure to complete the Session Feedback Form and sign the class roster in the back of the room

19 Session Feedback Form Summit 2007 Las Vegas, NV Please take a moment to evaluate this session and offer feedback. Activant uses your input to understand your needs and to determine future Summit sessions. Session Name: Session Number: Presenter s Name: How important is this topic to your job/company? Not Important Important Please rate the educational value you received from this session Low Value High Value 1. What software are you currently using? 2. How long have you personally used this software? 3. Describe the effectiveness of your instructor. 4. What is your overall evaluation of this session? 5. What could have been done to improve this session? 6. What sessions would you like to see presented at future conferences? 7. What issues will be critical to your business in the next months? Check here if you would like CPE credits. To receive credits, be sure to sign your name at the bottom of this form and sign the roster in the session room. Answering the following questions is OPTIONAL (but required for CPE Credits). Yes No Did this session meet your expectations, based on the description/objectives in the registration materials? Were the pre-requisite requirements stated in the course description appropriate? Did the session materials contribute to achieving the learning objectives? Did the equipment (screen, microphone, projector, etc.) in the room enhance the instruction? Was the time allotted for the session appropriate for the topic? Name: Company: