Sponsored Content
Special Forums News, Links, Events and Announcements Announcing collectl - new performance linux performance monitor Post 302142515 by MarkSeger on Friday 26th of October 2007 06:14:54 PM
Old 10-26-2007
Announcing collectl - new performance linux performance monitor

About 4 years ago I wrote this tool inspired by Rob Urban's collect tool for DEC's Tru64 Unix. What makes this tool as different as collect was in its day is its ability to run at a low overhead and collect tons of stuff. I've expanded the general concept and even include data not available in any other tool such as Infiniband or Lustre data. Collectl can collect it all and present it in a consistent output format. There's even an option to let you generate the data in plottable format.

Far to many features to talk about here but they are discussed on the website for collectl

Ever wonder why ALL tools that monitor linux network stats at 1 second intervals report the wrong numbers? The short answer is because the stats are only updated once ever 0.9765 seconds and unless you have a monitor that can run at fractional intervals like collectl, you'll get wrong numbers! You can read more about it on collectl's website but don't take my word for it. Download it and try it out.

-mark
 

8 More Discussions You Might Find Interesting

1. AIX

Performance Monitor

I am an old HP 3000 systems administrator who had to retire the 3000 for some nice pseries AIX boxes. We are a Symitar site and the powers that be do not think we are ready for root acess. I need to find ways within my chains to view system statistics. Being able to wow someone in management... (3 Replies)
Discussion started by: Beetlejuice
3 Replies

2. Red Hat

NFS performance stats on Linux

Hi everyone, The last two days I'm researching results of NFS operations on Linux, and I noticed some time difference when read and write. cat /proc/version : Linux version 2.6.9-42.ELsmp (bhcompile@hs20-bc1-1.build.redhat.com) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-2)) #1 SMP Wed Jul 12... (1 Reply)
Discussion started by: sysgate
1 Replies

3. HP-UX

API about system performance monitor

Hello, there. We want to write application on HP-UX to monitor system resource,such as CPU,Network Traffic Load,Disk Usage,etc. Anyone know these API functions except the system command ? thanks. (6 Replies)
Discussion started by: Frank2004
6 Replies

4. Red Hat

Linux disk performance

I am getting absolutely dreadful iowait stats on my disks when I am trying to install some applications. I have 2 physical disks on which I have created 2 separate logical volume groups and a logical volume in each. I have dumped some stats as below My dual core CPU is not being over utilised... (3 Replies)
Discussion started by: jimthompson
3 Replies

5. AIX

Tool to monitor the performance of the system ..

Dear experts , Pls advice for any good Tool to monitor the CPU and performance of AIX the system .. to keep monitoring to show me the utilization of that system .. (12 Replies)
Discussion started by: Mr.AIX
12 Replies

6. UNIX for Dummies Questions & Answers

Linux machine performance issue.

One of our database server is suddenly became very slow and i have no clue what to do .Please help. I m sharing the performance inforamtion regarding cpu,harddisk,ram . ########CPU Information######## Machine Uptime Information: uptime 10:25:06 up 16:50, 1 user, load average: 5.84, 5.65,... (10 Replies)
Discussion started by: pinga123
10 Replies

7. Programming

Tools to monitor system performance in Android or linux

Hi, May i know the tools which will give the below details in a consolidated fashion for some 'X' duration in single and multicore processors, 1) How many times and how long scheduler code and kernel threads are executing ? 2) Details about each process, time spent in each state (run, wait... (0 Replies)
Discussion started by: tkarthi85
0 Replies

8. Red Hat

Performance issue in Linux

IN solaris, for network high-availability we are using IPMP concept, can u tell me in REDHAT LINUX what we are using... also pls share good step to read & understand the that concept... Also performance issue in linux what are step & cmd can u tell me??? (2 Replies)
Discussion started by: tiger09
2 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:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy