01-22-2009
Sounds like a software's issue - tibco. If it's issue at all - in your case, those processes may just be greedy for memory. Such commercial applications should have Capacity planning documents, which should inform you about the Key System Resource Characteristics of certain product - how much disk space is being consumed over the time, what CPU and RAM memory you should expect on such hardware, etc.
However, if you're after memory leak, monitor the processes over the time and talk to their support people.
10 More Discussions You Might Find Interesting
1. Red Hat
What's the best way to find out how much memory is being used/available? I tried using free, but I didn't quite understand the output. Can someone explain it?
$ free
total used free shared buffers cached
Mem: 16304536 16256376 48160 0 ... (6 Replies)
Discussion started by: junkmail426
6 Replies
2. HP-UX
how can I find cpu usage memory usage swap usage and
I want to know CPU usage above X% and contiue Y times and memory usage above X % and contiue Y times
my final destination is monitor process
logical volume usage above X % and number of Logical voluage above
can I not to... (3 Replies)
Discussion started by: alert0919
3 Replies
3. UNIX for Dummies Questions & Answers
Hi ,
As I am new to Linux server, I am facing some doubts like: On linux server virtual memory usage goes to 99%, but I have Threshold limit of 95%. So it crossed the threshold limit and alarmd.
Yesterday I moniterd the server using TOP command, and found some of Tibco process was consuming... (1 Reply)
Discussion started by: Jaywantmm
1 Replies
4. AIX
How to monitor the IBM AIX server for I/O usage, memory usage, CPU usage, network usage, storage usage? (3 Replies)
Discussion started by: laknar
3 Replies
5. Shell Programming and Scripting
ok, so i'm trying to write a shell script (not perl) that monitors memory usage on a server. but i'm confused as to what fields exactly determines that yes, memory is low on a particular server.
it sounds simple enough, but it really isn't. what do I look for in the field below?
... (1 Reply)
Discussion started by: SkySmart
1 Replies
6. UNIX for Advanced & Expert Users
18:45:47 # free -m
total used free shared buffers cached
Mem: 96679 95909 770 0 1530 19550
-/+ buffers/cache: 74828 21851
Swap: 12287 652 11635
Hi all. The below output is from a RHEL 4.5... (0 Replies)
Discussion started by: drummerrob
0 Replies
7. UNIX for Advanced & Expert Users
Experts,
I have been trying to figure out what is the total physical memory used from this output:
And what is the free memory available for the application or any programs.
The answer has to be in this format:
1. Physical Memory Used= xx.xx%
2. Physical Memry available= yy.yy%
... (5 Replies)
Discussion started by: rveri
5 Replies
8. AIX
Hi All,
I have some questions regarding the performance, MEMORY/ Virtual Memory (paging /swap space)
Please see the nmon-MEMORY stats from my AIX LPAR.
24 GB --> RAM
3456 MB --> Paging Space
│ Memory ───────────────────────────────────────────────────────────────────────
│... (8 Replies)
Discussion started by: System Admin 77
8 Replies
9. Red Hat
Hi ,
There is one following alert .
Message : cdm:Average (2 samples) swap memory usage is now 91%, which is above the warning threshold (90%)
Here is my findings.
Output of TOP command in Linux server.
top - 14:21:44 up 6 days, 4:48, 1 user, load average: 2.55, 2.06,... (3 Replies)
Discussion started by: Maddy123
3 Replies
10. Shell Programming and Scripting
Hello
We are in the process of migrating few of our applications in our linux boxes to new linux box to streamline our applications . In this context , i would like to know how we can calculate a particular application is used .?
This data will then be used to select which applications need... (7 Replies)
Discussion started by: ron5174
7 Replies
RAM(4) Kernel Interfaces Manual RAM(4)
NAME
ram - ram disk driver
SYNOPSIS
/sys/conf/SYSTEM:
NRAM ram_size # RAM disk size (512-byte blocks)
major device number(s):
block: 3
minor device encoding:
must be zero (0)
DESCRIPTION
The ram pseudo-device provides a very fast extended memory store. It's use is intended for file systems like /tmp and applications which
need to access a reasonably large amount of data quickly.
The amount of memory dedicated to the ram device is controlled by the NRAM definition in units of 512-byte blocks. This is also patchable
in the system binary through the variable ram_size (though a patched system would have to be rebooted before any change took effect; see
adb(1)). This makes it easy to test the effects of different ram disk sizes on system performance. It's important to note that any space
given to the ram device is permanently allocated at system boot time. Dedicating too much memory can adversely affect system performance
by forcing the system to swap heavily as in a memory poor environment.
The block file accesses the ram disk via the system's buffering mechanism through a buffer sharing arrangement with the buffer cache. It
may be read and written without regard to physical disk records. There is no `raw' interface since no speed advantage is gained by such an
interface with the ram disk.
DISK SUPPORT
The ram driver does not support pseudo-disks (partitions). The special files refer to the entire `drive' as a single sequentially
addressed file.
A typical use for the ram disk would be to mount /tmp on it. Note that if this arrangement is recorded in /etc/fstab then /etc/rc will
have to be modified slightly to do a mkfs(8) on the ram disk before the standard file system checks are done.
FILES
/dev/ram block file
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO
hk(4), ra(4), rl(4), rk(4), rp(4), rx(4), si(4), xp(4) dtab(5), autoconfig(8)
DIAGNOSTICS
ram: no space. There is not enough memory to allocate the space needed by the ram disk. The ram disk is disabled. Any attempts to access
it will return an error.
ram: not allocated. No memory was allocated to the ram disk and an attempt was made to open it. Either not enough memory was available at
boot time or the kernel variable ram_size was set to zero.
BUGS
The ram driver is only available under 2.11BSD.
3rd Berkeley Distribution Januray 27, 1996 RAM(4)