Sponsored Content
Full Discussion: Performance monitoring
Operating Systems AIX Performance monitoring Post 74675 by jhansrod on Sunday 12th of June 2005 03:57:22 AM
Old 06-12-2005
Performance monitoring

Hi All

I am looking for a script that would collect statistics in a summarised format.
CPU, Memory,Swap, Wait queue, Run queue and disk activity.
Something that would allow me to profile the environment based on a 1 line output that I could run every 15 min.

Thx

Junaid
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

performance monitoring

hi, can any one tell me, is there is any way i can check the performance of my solaris 8 os on an Ent 3500. Other than top to check for the top most processes, how to make the calculations with vmstat, iostat, mpstat and nfsstat. Or is there any other tools that i can use? cheers. (3 Replies)
Discussion started by: i2admin
3 Replies

2. UNIX for Advanced & Expert Users

Performance Monitoring

Hi all The place I work for is about to to place there database server under heavy load for testing and would like the effect recorded as much as possible. Can anyone point me in the right direction with respect to real time system monitoring. I am aware of of 'sar', vmstat etc and hope to... (2 Replies)
Discussion started by: silvaman
2 Replies

3. UNIX for Dummies Questions & Answers

Performance monitoring

Hello, I am trying to find a way to view current CPU and disk usage. I used to use nmon which worked fine but since an upgrade to our servers this is no longer available. I have tried to get it reinstalled to no avail! Are there any other commands you can use within unix which will allow me... (4 Replies)
Discussion started by: johnwilliams
4 Replies

4. UNIX for Dummies Questions & Answers

Unix Performance Monitoring

In the vmstat , there are many columns you can see. Can someone tell me what is the most important column that i need to be watched on, and what value or average value should i watch inorder to determine that im experiencing a cpu bottle neck. What should be my basis. or if you use glance ... (2 Replies)
Discussion started by: kaibiganmi
2 Replies

5. Solaris

Performance Monitoring

Hi all, I am planning to give a presentation on performance measure. I have decided to focus on the commands which are used to know the performance of the server. I have a idea of prstat,vmstat,netstat, and iostat. Could anybody suggest me any other commands which are used for perforamance... (7 Replies)
Discussion started by: priky
7 Replies

6. Shell Programming and Scripting

Performance monitoring help needed.

How would i check for following? 1)open ports in my linux machine. 2)Hard disk read speed. 3)Hard disk write speed. (2 Replies)
Discussion started by: pinga123
2 Replies

7. AIX

Performance Monitoring of FileSystem

As I am new to the Unix field, I would like to get the clarification regarding the Filesystem. The scenario is.. The filesystem (/drbackup) is getting monitored and if it exceeds the threshold, we will receive an alert from it. The issue is that we receive an alert with the description of... (2 Replies)
Discussion started by: A.Srenivasan
2 Replies

8. Solaris

Performance / Batch monitoring

What tools can I use to look "deeper" into a process to see if the job is actually running or just hanging. What is the best method to accomplish this? SunOS 5.10 Generic_142900-14 sun4v sparc SUNW,T5240 (2 Replies)
Discussion started by: Harleyrci
2 Replies

9. AIX

Need some help for AIX performance monitoring

Hello I am new user of AIX; I have only basic knowledge of the UNIX commands, and I want to create script that will monitor the performance and resources usage on AIX 6.1 machine. Basically I wan to start a loop that will grab, every 10 seconds, the CPU usage, the memory usage, the disk usage,... (1 Reply)
Discussion started by: adaher
1 Replies

10. Red Hat

Performance Monitoring - RHEL 7.4

Have a question about doing some performance monitoring - how to approach it. This is on RHEL 7.4 We are moving a rather large application to new hardware in the future. I would like to find a way to compared performance on the new hardware at different stages and at different times. I'm... (4 Replies)
Discussion started by: Overcast451
4 Replies
PMCOLLECTL(1)						      General Commands Manual						     PMCOLLECTL(1)

NAME
pmcollectl - collect data that describes the current system status SYNOPSIS
pmcollectl [-f file | -p file ...] [options ...] DESCRIPTION
pmcollectl is a system-level performance monitoring utility that records or displays specific operating system data for one or more sets of subsystems. Any of the subsystems (such as CPU, Disks, Memory or Sockets) can be included or excluded from data collection. Data can either be displayed immediately to a terminal, or stored in files for retrospective analysis. pmcollectl is a python(1) script providing much of the functionality available from the collectl(1) Linux utility (which happens to be written in perl(1)). It makes use of the Performance Co-Pilot (PCP) toolkit to simplify its implementation, as well as provide more of the collectl functional- ity on platforms other than Linux. pmcollectl has two primary modes of operation: 1. Record Mode (-f or --filename option) which reads data from a live system and writes output to a file or displays it on a terminal. 2. Playback Mode (-p or --playback option) which reads data from one or more PCP archive files and displays output on a terminal. Note that these files are not raw collectl format data, rather they are archives created by the pmlogger(1) utility (possibly indirectly, through use of the -f option to pmcollectl). RECORD MODE OPTIONS
In this mode data is taken from a live system and either displayed on the terminal or written to a PCP archive. -h host Display metrics from host instead of displaying metrics from the local host. -c, --count samples The number of samples to record. -f, --filename filename This is the name of a PCP archive to write the output to. -i, --interval interval This is the sampling interval in seconds. The default is 1 second. -R, --runtime duration Specify the duration of data collection where the duration is a number followed by one of wdhms, indicating how many weeks, days, hours, minutes or seconds the collection is to be taken for. PLAYBACK MODE OPTIONS
In this mode, data is read from one or more PCP data files that were generated with the recording option, or indirectly via the pmlogger utility. -f, --filename filename If specified, this is the name of a PCP archive to write the output to (rather than the terminal). -p, --playback filename Read data from the specified PCP archive files(s). COMMON OPTIONS
The following options are supported in both record and playback modes. --help Display standard help message. -s, --subsys subsystem This field controls which subsystem data is to be collected or played back for. The rules for displaying results vary depending on the type of data to be displayed. If you write data for CPUs and DISKs to a raw file and play it back with -sc, you will only see CPU data. If you play it back with -scm you will still only see CPU data since memory data was not collected. To see the current set of default subsystems, which are a subset of this full list, use -h. The default is "cdn", which stands for CPU, Disk and Network summary data. SUMMARY SUBSYSTEMS c - CPU d - Disk f - NFS V3 Data j - Interrupts m - Memory n - Networks y - Slabs (system object caches) DETAIL SUBSYSTEMS This is the set of detail data from which in most cases the corresponding summary data is derived. So, if one has 3 disks and chooses -sd, one will only see a single total taken across all 3 disks. If one chooses -sD, individual disk totals will be reported but no totals. C - CPU D - Disk F - NFS Data J - Interrupts M - Memory node data, which is also known as NUMA data N - Networks Y - Slabs (system object caches) Z - Processes --verbose Display output in verbose mode. This often displays more data than in the default mode. When displaying detail data, verbose mode is forced. Furthermore, if summary data for a single subsystem is to be displayed in verbose mode, the headers are only repeated occasionally whereas if multiple subsystems are involved each needs their own header. SEE ALSO
PCPIntro(1), collectl(1), perl(1), python(1), pmlogger(1), pmcd(1), pmprobe(1), pmval(1), PMAPI(3), and pcp.conf(5). Performance Co-Pilot PCP PMCOLLECTL(1)
All times are GMT -4. The time now is 02:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy