Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Unix performance monitoring counters Post 302100514 by gen4ik on Wednesday 20th of December 2006 07:49:09 AM
Old 12-20-2006
Unix performance monitoring counters

Which performance counters you might to define as "The most important counters in checking unix performance"
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix performance monitoring via Windows/NT

We are trying to Monitor Unix via Window95/98 on an NT network. Is there anyone that could point us in the direction on software that runs in Windows on a Telnet connection that we could use to accomplish this? We have tried a program called Unix Watcher by Etasoft and can' get it to connect. ... (6 Replies)
Discussion started by: btrout
6 Replies

2. 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

3. 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

4. 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

5. 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

6. Linux

Linux/Unix performance monitoring

This is my first post (yes I'm a newbie).... :D I'm looking for a list of Linux and Unix commands for performance monitoring and a good sight or area on this site that would have man pages and or information on those commands..... Thanks if anyone can take the time to post..... :cool: (14 Replies)
Discussion started by: harrisjl
14 Replies

7. 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

8. Shell Programming and Scripting

Performance Monitoring script for UNIX servers

Hi, I have been working on writing an automated script that will run 24x7 to monitor the performance parameters like CPU,Memory,Disk I/O,Network,SWAP Space etc for all types of Unix servers ( HP-UX,AIX,SOLARIS,LINUX). Problem is I am confused with the commands top,prstat,vmstat,free,sar etc.... (4 Replies)
Discussion started by: ssk250
4 Replies
cpc_shared_open(3CPC)													     cpc_shared_open(3CPC)

NAME
cpc_shared_open, cpc_shared_bind_event, cpc_shared_take_sample, cpc_shared_rele, cpc_shared_close - use CPU performance counters on proces- sors SYNOPSIS
cc [ flag... ] file... -lcpc [ library... ] #include <libcpc.h> int cpc_shared_open(void); int cpc_shared_bind_event(int fd, cpc_event_t *event, int flags); int cpc_shared_take_sample(int fd, cpc_event_t *event); int cpc_shared_rele(int fd); void cpc_shared_close(int fd); The cpc_shared_open() function allows the caller to access the hardware counters in such a way that the performance of the currently bound CPU can be measured. The function returns a file descriptor if successful. Only one such open can be active at a time on any CPU. The cpc_shared_bind_event(), cpc_shared_take_sample(), and cpc_shared_rele() functions are directly analogous to the corresponding cpc_bind_event(), cpc_take_sample(), and cpc_rele() functions described on the cpc_bind_event(3CPC)manual page, except that they operate on the counters of a particular processor. USAGE
If a thread wishes to access the counters using this interface, it must do so using a thread bound to an lwp, (see the THR_BOUND flag to thr_create(3C)), that has in turn bound itself to a processor using processor_bind(2). Unlike the cpc_bind_event(3CPC) family of functions, no counter context is attached to those lwps, so the performance counter samples from the processors reflects the system-wide usage, instead of per-lwp usage. The first successful invocation of cpc_shared_open() will immediately invalidate all existing performance counter context on the system, and prevent all subsequent attempts to bind counter context to lwps from succeeding anywhere on the system until the last caller invokes cpc_shared_close(). This is because it is impossible to simultaneously use the counters to accurately measure per-lwp and system-wide events, so there is an exclusive interlock between these uses. Access to the shared counters is mediated by file permissions on a cpc pseudo device. Only a user with the {PRIV_SYS_CONFIG} privilege is allowed to access the shared device. This control prevents use of the counters on a per-lwp basis to other users. The CPC_BIND_LWP_INHERIT and CPC_BIND_EMT_OVF flags are invalid for the shared interface. On success, the functions (except for cpc_shared_close()) return 0. On failure, the functions return -1 and set errno to indicate the rea- son. EACCES The caller does not have appropriate privilege to access the CPU performance counters system-wide. EAGAIN For cpc_shared_open(), this value implies that the counters on the bound cpu are busy because they are already being used to measure system-wide events by some other caller. EAGAIN Otherwise, this return value implies that the counters are not available because the thread has been unbound from the pro- cessor it was bound to at open time. Robust programs should be coded to expect this behavior, and should invoke cpc_shared_close(), before retrying the operation. EINVAL The counters cannot be accessed on the current CPU because the calling thread is not bound to that CPU using proces- sor_bind(2). ENOTSUP The caller has attempted an operation that is illegal or not supported on the current platform. ENXIO The current machine either has no performance counters, or has been configured to disallow access to them system-wide. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ |Interface Stability |Obsolete | +-----------------------------+-----------------------------+ processor_bind(2), cpc(3CPC), cpc_bind_cpu(3CPC), cpc_bind_event(3CPC), cpc_set_sample(3CPC), cpc_unbind(3CPC), libcpc(3LIB), thr_cre- ate(3C), attributes(5) The cpc_shared_open(), cpc_shared_bind_event(), cpc_shared_take_sample(), cpc_shared_rele(), and cpc_shared_close() functions exist for binary compatibility only. Source containing these functions will not compile. These functions are obsolete and might be removed in a future release. Applications should use cpc_bind_cpu(3CPC), cpc_set_sample(3CPC), and cpc_unbind(3CPC) instead. 28 Mar 2005 cpc_shared_open(3CPC)
All times are GMT -4. The time now is 02:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy