02-03-2004
I don't know where you got that .3 but it's way too low. You have double digit idle times on every cpu. You do have two processes that spend 98% of their time in the cpu. The kernel knows this and has given them a nasty priority. They only run when nothing else wants to. Since you have double digit idle times on each of your four cpu's, yes they run a lot.
HP has a product called glance or maybe it's glance-plus now. It looks like you can download a trial version
here. Try it. It will tell where your bottlenecks are.
10 More Discussions You Might Find Interesting
1. UNIX and Linux Applications
Ello group,
I have general question about how the performance of server/client should be?
My server is able to answer about 650times per second. Is it good performance?
the apache on the same machine makes 1600/sec BUT there is nine instances of httpd daemon what makes 180/ sec /instance.
of... (1 Reply)
Discussion started by: tomjan
1 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I am supposed to run few jobs based on the usage of unix server. How to find out if the server is too busy. what are the commands we can use to find out that.
Thanks (1 Reply)
Discussion started by: dnat
1 Replies
3. Solaris
Hi,
i would like to ask if it is possible to get the server load on a solaris machine, but i don't want something like uptime (load average), iostat and vmstat. I would like to get something in percentage like CPU load in %, Disk usage in %, Ram usage in %.
I want to collect this data and to... (3 Replies)
Discussion started by: tafil
3 Replies
4. Solaris
Hi,
Please advice .. if server is slowness then what are the steps i have to follow...
Thanks,
Mani (5 Replies)
Discussion started by: Mani_apr08
5 Replies
5. Infrastructure Monitoring
There is a big problem with the server (VPS based on OpenVZ, CentOS 5, 3GB RAM). The problem is the following. The first 15-20 minutes after starting the server is operating normally, the load average is less than or about 1.0, but then begins to increase sharply% wa, then hovers around 95-99%.... (2 Replies)
Discussion started by: draiphod
2 Replies
6. Solaris
hi all,
My server box is slow running. I have provide some statistics below:
Where is the bottleneck on the server?
I guess the bottleneck is disk I/O?
bash-3.00# prstat -Z
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
29206 mobi1 334M 264M sleep ... (8 Replies)
Discussion started by: buyantugs
8 Replies
7. AIX
Hi,
I am new registered user here in this UNIX forums.
I am a new system administrator for AIX 6.1. One of our servers performs poorly every time our application (FINACLE) runs many processes/instances. (see below for topas snapshot)
I use NMON or Topas to monitor the server utilization. I... (9 Replies)
Discussion started by: guzzelle
9 Replies
8. UNIX for Advanced & Expert Users
Hi,
how can we define performance of a server (Windows or Unix or Linux) ?
If processes waiting for CPU (on queue) are usually more than 3 or 5 can we conclude that CPU is not enough for that usage ?
Thank you. (1 Reply)
Discussion started by: big123456
1 Replies
9. Red Hat
Hi Guys,
I am running Oracle database on RHEL 2.6.18-164.el5, now I want to check and make sure that my server is performing optimally.
I check top:
top - 09:45:03 up 2 days, 15:22, 3 users, load average: 2.57, 2.85, 2.77
Tasks: 433 total, 3 running, 430 sleeping, 0 stopped, 0... (1 Reply)
Discussion started by: Phuti
1 Replies
10. UNIX for Advanced & Expert Users
We are wondering if we are facing performance issue in our server when running Informatica jobs. Two things to suspect:
cache memory never comes down even when Top shows > 99% used.
There is some contention io or network related or Cache is clogged
top - 20:58:20 up 16 days, ... (3 Replies)
Discussion started by: smart_guy471
3 Replies
LEARN ABOUT CENTOS
pmdaapache
PMDAAPACHE(1) General Commands Manual PMDAAPACHE(1)
NAME
pmdaapache - Apache2 web server performance metrics domain agent (PMDA)
SYNOPSIS
$PCP_PMDAS_DIR/apache/pmdaapache [-d domain] [-l logfile] [-U username] [-S server] [-P port] [-L location]
DESCRIPTION
pmdaapache is a Performance Metrics Domain Agent (PMDA) which extracts performance metrics describing the state of an Apache web server.
The apache PMDA exports metrics that measure the request rate, cumulative request sizes, uptime and various connection states for active
clients.
This information is obtained by performing a HTTP request to the server status URL, which must be enabled in the httpd.conf configuration
file.
ExtendedStatus on
<Location /server-status>
SetHandler server-status
Order deny,allow
Deny from all
Allow from localhost
</Location>
A brief description of the pmdaapache command line options follows:
-d It is absolutely crucial that the performance metrics domain number specified here is unique and consistent. That is, domain should
be different for every PMDA on the one host, and the same domain number should be used for the same PMDA on all hosts.
-l Location of the log file. By default, a log file named apache.log is written in the current directory of pmcd(1) when pmdaapache is
started, i.e. $PCP_LOG_DIR/pmcd . If the log file cannot be created or is not writable, output is written to the standard error
instead.
-S Query the Apache status information from the named server rather than the local host.
-P Query the Apache status information from the given port rather than the default (80).
-L Specify an alternative location for finding the server-status page.
-U User account under which to run the agent. The default is the unprivileged "pcp" account in current versions of PCP, but in older
versions the superuser account ("root") was used by default.
INSTALLATION
If you want access to the names, help text and values for the apache performance metrics, do the following as root:
# cd $PCP_PMDAS_DIR/apache
# ./Install
If you want to undo the installation, do the following as root:
# cd $PCP_PMDAS_DIR/apache
# ./Remove
pmdaapache is launched by pmcd(1) and should never be executed directly. The Install and Remove scripts notify pmcd(1) when the agent is
installed or removed.
FILES
$PCP_PMCDCONF_PATH
command line options used to launch pmdaapache
$PCP_PMDAS_DIR/apache/help
default help text file for the apache metrics
$PCP_PMDAS_DIR/apache/Install
installation script for the pmdaapache agent
$PCP_PMDAS_DIR/apache/Remove
undo installation script for the pmdaapache agent
$PCP_LOG_DIR/pmcd/apache.log
default log file for error messages and other information from pmdaapache
PCP ENVIRONMENT
Environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP. On each installation, the
file /etc/pcp.conf contains the local values for these variables. The $PCP_CONF variable may be used to specify an alternative configura-
tion file, as described in pcp.conf(5).
SEE ALSO
PCPIntro(1), httpd(8), pmcd(1), pcp.conf(5) and pcp.env(5).
Performance Co-Pilot PCP PMDAAPACHE(1)