Hi,
I am seeing very high kernel usage and very high load averages on my system (Although we are not loading much data to our database). Here is the output of top...does anyone know what i should be looking at?
Thanks,
Lorraine
last pid: 13144; load averages: 22.32, 19.81, 16.78 ... (4 Replies)
Hi,
I am a nw bie to Schell Scripting, i have a same king of requirement as posted above.
my input file is also a log file as below.....
28.05.2008 07:02:56,105 INFO Validation request recieved
28.05.2008 07:03:57,856 INFO 0:01:13.998 Response sent with: <?xml version="1.0"... (0 Replies)
Hello Unix gurus,
I have a Solaris 8 system on which since last few days we are noticing 0% idle state. When I checked with sar utility, I saw that process switching is very high. The output of sar -w is pasted below:
sar -w 3 20
SunOS bdspb306 5.8 Generic_108528-18 sun4u 06/24/08
... (0 Replies)
i have a Intel Quad Core Xeon X3440 (4 x 2.53GHz, 8MB Cache, Hyper Threaded) with 16gig and 1tb harddrive with a 1gb port and my apache is causing my cpu to go up to 100% on all four cores heres my http.config
<IfModule prefork.c>
StartServers 10
MinSpareServers 10
MaxSpareServers 15... (4 Replies)
Hi ,
I am trying to :wall: my head while scripting ..I am really new to this stuff , never did it before :( .
how to find cpu's system high time and user time high in a script??
thanks , help would be appreciated !
:) (9 Replies)
Hi ,
We found CPU is high due to python process .Is this something that Oracle team should look on or Unix team has to work on it ?Could you please advise use of python process ?
top - 12:03:03 up 43 days, 15:11, 5 users, load average: 1.53, 1.33, 1.23
Tasks: 126 total, 3 running, 123... (12 Replies)
hi guys
I posted problem last time I didn't find answer to my issue.
my problem is as below:
I have two servers which work as an actif/standby in high availability system.
but when i use command HASTAT -a i have the following message: couldn' find actif node.
the servers are sun... (1 Reply)
Discussion started by: zineb06
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)