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
MLOCK(2) Linux Programmer's Manual MLOCK(2)
NAME
mlock - disable paging for some parts of memory
SYNOPSIS
#include <sys/mman.h>
int mlock(const void *addr, size_t len);
DESCRIPTION
mlock disables paging for the memory in the range starting at addr with length len bytes. All pages which contain a part of the specified
memory range are guaranteed be resident in RAM when the mlock system call returns successfully and they are guaranteed to stay in RAM until
the pages are unlocked by munlock or munlockall, until the pages are unmapped via munmap, or until the process terminates or starts another
program with exec. Child processes do not inherit page locks across a fork.
Memory locking has two main applications: real-time algorithms and high-security data processing. Real-time applications require determin-
istic timing, and, like scheduling, paging is one major cause of unexpected program execution delays. Real-time applications will usually
also switch to a real-time scheduler with sched_setscheduler. Cryptographic security software often handles critical bytes like passwords
or secret keys as data structures. As a result of paging, these secrets could be transfered onto a persistent swap store medium, where they
might be accessible to the enemy long after the security software has erased the secrets in RAM and terminated.
Memory locks do not stack, i.e., pages which have been locked several times by calls to mlock or mlockall will be unlocked by a single call
to munlock for the corresponding range or by munlockall. Pages which are mapped to several locations or by several processes stay locked
into RAM as long as they are locked at least at one location or by at least one process.
On POSIX systems on which mlock and munlock are available, _POSIX_MEMLOCK_RANGE is defined in <unistd.h> and the value PAGESIZE from <lim-
its.h> indicates the number of bytes per page.
NOTES
With the Linux system call, addr is automatically rounded down to the nearest page boundary. However, POSIX 1003.1-2001 allows an imple-
mentation to require that addr is page aligned, so portable applications should ensure this.
RETURN VALUE
On success, mlock returns zero. On error, -1 is returned, errno is set appropriately, and no changes are made to any locks in the address
space of the process.
ERRORS
ENOMEM Some of the specified address range does not correspond to mapped pages in the address space of the process or the process tried to
exceed the maximum number of allowed locked pages.
EPERM The calling process does not have appropriate privileges. Only root processes are allowed to lock pages.
EINVAL len was not a positive number.
CONFORMING TO
POSIX.1b, SVr4. SVr4 documents an additional EAGAIN error code.
SEE ALSO
mlockall(2), munlock(2), munlockall(2), munmap(2), setrlimit(2)
Linux 1.3.43 1995-11-26 MLOCK(2)