I have checked other servers having the same OS,hardware and almost having same workload.Their buffer cache values are as below. Their utilizations are < 40%. So I hope this buffer cache may be the culprit for displaying high utilization.
Thanks for everyone for your help in this. I cant say this was closed but hope that this may help to close this problem. Let's see what happens if these values are changed.
Code:
Parameter Current Dyn Planned Module Version
===============================================================================
dbc_max_pct 9 - 9
dbc_min_pct 5 - 5
Hi am facing high cpu utilization on my sybase server.
I have P550
Number Of Processors: 4
Processor Clock Speed: 1656 MHz
CPU Type: 64-bit
Kernel Type: 32-bit
LPAR Info: 1 65-D837E
Memory Size: 7840 MB
in topas it shows
Name PID CPU% PgSp Owner
dataserv 565264 ... (1 Reply)
Hi Unix Gurus i am somewhat new to unix scripting so need your help to
create a script as below.
# This script would find the process consuming memory beyond a certain #limit. if the meemory consumption is more than 100% for a period of 1
# minute for the specific process. the script would... (0 Replies)
Hi,
i have two oracle instances running on my server with 7.5G RAM but it is showing almost 99% memory is full as you can see bellow.
# svmon
size inuse free pin virtual
memory 1974272 1954270 20002 336595 1800652
pg space 4194304 ... (7 Replies)
How to find the memory utilization of AIX server using svmon -G output.
Sample output for svmon -G command from my AIX test server,
size inuse free pin virtual
memory 4014080 3995443 18637 575916 1876393
pg space 1179648 ... (3 Replies)
Hello All,
We have a jave server running on both linux and Solaris environments.
On solaris,it consumes only 600-700MB whereas it goes upto 21G in Linux.
I am monitoring the memory consumption through top command.
Is this high memory consumption expected in Linux? (1 Reply)
Hi Experts,
Our servers running Solaris 10 with SAP Application. The memory utilization always >90%, but the process on SAP is too less even nothing.
Why memory utilization on solaris always looks high?
I have statement about memory on solaris, is this true:
Memory in solaris is used for... (4 Replies)
Hello Guys,
I have one Solaris server with high memory utilization >90%. As per checking, below is the output for memory usage.
bash-3.00# ps -efo pmem,uid,pid,ppid,pcpu,comm | sort -r
%MEM UID PID PPID %CPU COMMAND
1.7 29496 20668 1 0.0 /opt/app/iw-home/tools/java/bin/java
1.5... (1 Reply)
Hi All,
I have a java process which is showing high virtual memory utilization in client server. But the same process is showing comparitively lesser virtual memory consumption. I understand that virtual memory shown is not of much importance for the general user in normal condition, my client... (2 Replies)
Hi,
i am new to linux/RHEL 6.0 and i have two questions.
1) How to get the CPU utilization and Memory Utilization of all Services running currently?
2) How to get the CPU utilization and Memory Utilization of all Applications running currently?
Please help me to find the script.
... (2 Replies)
Hi Fellas,
Not sure how I can dig in even further but we notice that one of our DB servers is showing high Sys% CPU usage even though when I execute the following command :
I can see that postgres is the only one using the CPU. So if anyone can advise me what would be the best way to... (3 Replies)
Discussion started by: arizah
3 Replies
LEARN ABOUT HPUX
vxcached
vxcached(1M)vxcached(1M)NAME
vxcached - resize cache volumes when required
SYNOPSIS
/etc/vx/bin/vxcached [-v] [mail-address ...]
DESCRIPTION
The Veritas Volume Manager cache daemon, vxcached, is invoked by the VxVM kernel to monitor the cache objects that are used by space-opti-
mized snapshots. When usage of a cache volume by space-optimized snapshots reaches the high watermark level that has been set for the
cache, vxcached automatically grows the cache volume if this is required and configured.
The -v option enables the daemon in verbose mode. If no mail addresses are given as arguments, mail is sent to root.
If the autogrow feature has been enabled on a cache object, the values of the highwatermark, autogrowby and maxautogrow attributes for the
cache object determine the behavior of vxcached:
o When cache usage reaches the high watermark value, highwatermark, (default value is 90 percent), and the new required cache size would
not exceed the value of maxautogrow (default value is twice the size of the cache volume in blocks), vxcached grows the size of the
cache volume by the value of autogrowby (default value is 20% of the size of the cache volume in blocks).
o When cache usage reaches the high watermark value, and the new required cache size would exceed the value of maxautogrow, vxcached
deletes the oldest snapshot in the cache. If there are several snapshots with the same age, the largest of these is deleted.
If the autogrow feature has been disabled on a cache object:
o When cache usage reaches the high watermark value, vxcached deletes the oldest snapshot in the cache. If there are several snapshots
with the same age, the largest of these is deleted. If there is only a single snapshot, the snapshot is detached and marked as invalid.
The values of the highwatermark, autogrowby and maxautogrow attributes can be set when a cache object is created using vxmake. If neces-
sary, you can use the vxcache set command to change the values of these attributes for an existing cache.
NOTES
The vxcached daemon is started automatically if a license for the FastResync feature is already present on the system. If you add such a
license while VxVM is running, you can either start vxcached manually, or shut down and reboot the system.
Killing the vxcached process stops it from removing snapshots. The daemon can be prevented from being started by commenting out its entry
in the startup script, /sbin/init.d/vxvm-recover.
The vxcached daemon does not remove snapshots that are currently open, and it does not remove the last or only snapshot in the cache.
If the cache space becomes exhausted, the snapshot is detached. If this happens, the snapshot is unrecoverable and must be removed manu-
ally. Enabling the autogrow feature on the cache helps to avoid this situation occurring. However, for very small caches (of the order of
a few megabytes), it is possible for the cache to become exhausted before the system has time to respond and grow the cache. In such
cases, either increase the size of the cache manually, or reduce the value of highwatermark.
You can use the maxautogrow attribute to limit the maximum size to which a cache can grow. To estimate this size, consider how much the
contents of each source volume are likely to change between snapshot refreshes, and allow some additional space for contingency.
SEE ALSO vxcache(1M), vxintro(1M), vxmake(1M), vxsnap(1M)VxVM 5.0.31.1 24 Mar 2008 vxcached(1M)