01-13-2012
The figures in the User CPU "us" column are high for a database system. Have you checked for looping orphan prococeses ?
10 More Discussions You Might Find Interesting
1. Solaris
Hi to all,
i have an app on solaris 5.8 writed in C++ (3.2.1) that use multi threading.
Hardware has 8 cpu. When i run my app i note that the average of cpu go at least at 40%, and the performance are not so higher..
There is a cpu limitation on solaris, that dedicate only a part of cpu... (3 Replies)
Discussion started by: Moodie
3 Replies
2. Solaris
Hi All,
In my application malloc is returning NULL even though there is sufficient amount of free memory is available but swap memory is low.
Is this possible that, if free memory is high & swap memory is low, malloc will not be able to allocate memory & return NULL ?:)
Kindly look into... (5 Replies)
Discussion started by: Ritesh Kumar
5 Replies
3. Shell Programming and Scripting
on the file Ftp'd from the mainframe ,do we have any UNIX command to replace mainframe low and values to space or null.
i tried using tr and it doesn't work ...
Thanks (1 Reply)
Discussion started by: rlmadhav
1 Replies
4. Shell Programming and Scripting
Is it possible to have a bash script pick the highest and lowest values of four variables? I've been googling for this but haven't come up with anything. I have a script that assigns variables ($c0, $c1, $c2, and $c3) based on the coretemps from grep/sed statements of sensors. I'd like to also... (5 Replies)
Discussion started by: graysky
5 Replies
5. Shell Programming and Scripting
Hi guys,
i have a question about spliting a binary file into 2 chunks.
First chunk with all high bytes and the second one with all low bytes.
What unix tools can i use? And how can this be performed?
I looked in manpages of split and dd but this does not help.
Thanks (2 Replies)
Discussion started by: basta
2 Replies
6. HP-UX
There might be some problem with my server,
because every morning at 7, it's performance become bad with no DB extra deadlock.
But I just couldn't figure it out.
Please give me some advise, thanks a lot...
According to the CPU performace chart, Daily CPU loading Maximum: 42 %, Average:36%.
... (8 Replies)
Discussion started by: GreenShery
8 Replies
7. UNIX for Dummies Questions & Answers
Need some clarification on this....
1. how are kernel/ user spaces and high/low memory related?
2. What do they all mean when i have the kernel command line as:
"console=ttyS0,115200 root=/dev/sda2 rw mem=exactmap memmap=1M@0 memmap=96M@1M irqpoll"
or
2. what do mem and memmap mean in... (3 Replies)
Discussion started by: dragonpoint
3 Replies
8. AIX
Hi
I am running AIX 5.2. My server is running low on memory. It it using about 1307775 file pages on a total of 1511424 (from vmstat -v).
I looked at the memory yesterday morning, and we had plenty of free memory. I did a backup from Windows (ftp mget command) of a large file selection. From... (5 Replies)
Discussion started by: fredrivard
5 Replies
9. Red Hat
Hi team
I have three physical servers running on Red Hat Enterprise Linux Server release 6.2 with the following memory conditions:
# cat /proc/meminfo | grep -i mem
MemTotal: 8062888 kB
MemFree: 184540 kB
Shmem: 516 kB
and the following swap conditions:
... (6 Replies)
Discussion started by: hedkandi
6 Replies
10. UNIX for Advanced & Expert Users
Could I please get some recommendations of a linux live cd for low memory? (1 Reply)
Discussion started by: cokedude
1 Replies
LEARN ABOUT REDHAT
slabinfo
SLABINFO(5) Linux manual SLABINFO(5)
NAME
/proc/slabinfo - Kernel slab allocator statistics
SYNOPSIS
cat /proc/slabinfo
DESCRIPTION
Frequently used objects in the Linux kernel (buffer heads, inodes, dentries, etc.) have their own cache. The file /proc/slabinfo gives
statistics. For example:
% cat /proc/slabinfo
slabinfo - version: 1.1
kmem_cache 60 78 100 2 2 1
blkdev_requests 5120 5120 96 128 128 1
mnt_cache 20 40 96 1 1 1
inode_cache 7005 14792 480 1598 1849 1
dentry_cache 5469 5880 128 183 196 1
filp 726 760 96 19 19 1
buffer_head 67131 71240 96 1776 1781 1
vm_area_struct 1204 1652 64 23 28 1
...
size-8192 1 17 8192 1 17 2
size-4096 41 73 4096 41 73 1
...
For each slab cache, the cache name, the number of currently active objects, the total number of available objects, the size of each object
in bytes, the number of pages with at least one active object, the total number of allocated pages, and the number of pages per slab are
given.
Note that because of object alignment and slab cache overhead, objects are not normally packed tightly into pages. Pages with even one in-
use object are considered in-use and cannot be freed.
Kernels compiled with slab cache statistics will also have "(statistics)" in the first line of output, and will have 5 additional columns,
namely: the high water mark of active objects; the number of times objects have been allocated; the number of times the cache has grown
(new pages added to this cache); the number of times the cache has been reaped (unused pages removed from this cache); and the number of
times there was an error allocating new pages to this cache. If slab cache statistics are not enabled for this kernel, these columns will
not be shown.
SMP systems will also have "(SMP)" in the first line of output, and will have two additional columns for each slab, reporting the slab
allocation policy for the CPU-local cache (to reduce the need for inter-CPU synchronization when allocating objects from the cache). The
first column is the per-CPU limit: the maximum number of objects that will be cached for each CPU. The second column is the batchcount:
the maximum number of free objects in the global cache that will be transferred to the per-CPU cache if it is empty, or the number of
objects to be returned to the global cache if the per-CPU cache is full.
If both slab cache statistics and SMP are defined, there will be four additional columns, reporting the per-CPU cache statistics. The
first two are the per-CPU cache allocation hit and miss counts: the number of times an object was or was not available in the per-CPU cache
for allocation. The next two are the per-CPU cache free hit and miss counts: the number of times a freed object could or could not fit
within the per-CPU cache limit, before flushing objects to the global cache.
It is possible to tune the SMP per-CPU slab cache limit and batchcount via:
echo "cache_name limit batchcount" > /proc/slabinfo
AVAILABILITY
/proc/slabinfo exists since Linux 2.1.23. SMP per-CPU caches exist since Linux 2.4.0-test3.
FILES
<linux/slab.h>
2001-06-19 SLABINFO(5)