07-09-2009
That big honking thing leaking 40% of your RAM and counting looks like your X server. Note how its actual memory consumption is way higher than the amount still paged in(RSS), its allocating lots of memory, not using it, and having it paged out to make room for more! Try upgrading it.
(You can avoid the lines getting cut off by redirecting ps into a file or pipe, by the way.)
Last edited by Corona688; 07-09-2009 at 03:37 PM..
9 More Discussions You Might Find Interesting
1. Programming
Hi, I try to marshal a unsigned int and a char * into a buffer, and then unmarshal them later to get them out. I need to put the char * in the front and unsigned int at the end of the buffer. However, my system always give me "BUS ERROR". I am using Sun Sparcs Sloris 2.10.
My code to marshal... (6 Replies)
Discussion started by: nj302
6 Replies
2. HP-UX
Refer from title:
How can i get memory used or anything that can show memory from sar file
example on solaris:-
we can use sar with option to show memory used at time that sar crontab run.
on HP-UX, it not has option to see memory used. But i think it may be have some parameter or some... (1 Reply)
Discussion started by: panithat
1 Replies
3. AIX
Hi,
Would any one be so kind to explain me :
are ulimits defined for each user seperately ? When ?
Specialy what is the impact of :
max locked memory
and
virtual memory
on performance of applications for a user.
Many thanks.
PS :
this is what I can see in MAN :
ulimit ]
... (5 Replies)
Discussion started by: big123456
5 Replies
4. Solaris
Hi,
Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:-
1. Total Physical Memory in the system(total RAM).
2. Available Physical Memory(i.e. RAM Usage)
3. Total (Logical) Memory in the system
4. Available (Logical) Memory.
I know... (4 Replies)
Discussion started by: 0ktalmagik
4 Replies
5. Programming
Hi,
I'm trying to learn how to manage memory when I have to deal with lots of data.
Basically I'm indexing a huge file (5GB, but it can be bigger), by creating tables that
holds offset <-> startOfSomeData information. Currently I'm mapping the whole file at
once (yep!) but of course the... (1 Reply)
Discussion started by: emitrax
1 Replies
6. Solaris
Is it possible to restrict physical memory in solaris zone with zone.max-locked-memory just like we can do with rcapd ? I do not want to used rcapd (1 Reply)
Discussion started by: fugitive
1 Replies
7. UNIX for Advanced & Expert Users
I was running a program and it stopped and showed "Out of Memory!". at that time, the RAM used by this process is around 4G and the free memory size of the machine is around 30G. Does anybody know what maybe the reason? this program is written with Perl. the OS of the machine is Solaris U8. And I... (1 Reply)
Discussion started by: lilili07
1 Replies
8. Solaris
Hello solaris experts,
Being new to solaris containers, from Linux, feeling difficulty in understanding certain concepts. Hope somebody can help me here.
I understand that, & some questions ....
Locked memory -- memory which will not be swapped out at any cause.
is this for... (0 Replies)
Discussion started by: thegeek
0 Replies
9. Solaris
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)
Discussion started by: edydsuranta
4 Replies
LEARN ABOUT HPUX
fcache_seqlimit_system
fcache_seqlimit_system(5) File Formats Manual fcache_seqlimit_system(5)
NAME
fcache_seqlimit_system - percentage of file cache that can be consumed by sequential accesses, per system-wide limit
VALUES
Failsafe
Default
Allowed values
The minimum value allowed is The maximum value allowed is
Specify a positive integer value.
DESCRIPTION
This parameter places a system-wide limit on how much memory can be consumed in the file cache by sequential accesses. It is important to
note the relationship between this tunable and the per-file limit tunable, These two tunables, in conjunction, control how much memory in
the file cache can be consumed by sequential accesses.
When sequential accesses to a file has exceeded the per-file limit AND the system-wide limit, the excess file cache pages are paged out.
Note that both limits have to be reached in order for page stealing to occur. For example, a file can exceed its limit if the limit has
not been reached. Similarly, no page stealing occurs if none of the files on the system has exceeded the per-file limit, even if the sys-
tem-wide limit has been hit.
The page stealing feature is specific to improving sequential I/O performance for large files. Limiting file cache memory consumption
helps alleviate memory pressure in the file cache. It also prevents cache wiping -- a single thread sequentially accessing a large file
can wipe out the existing contents of the file cache.
Who is Expected to Change This Tunable?
System administrators that run applications which do large sequential file I/O's. Typically, these files are larger than the size of phys-
ical memory on the system.
Restrictions on Changing
Changes to this tunable take effect immediately.
When Should the Value of This Tunable Be Raised?
When you wish to allow greater file cache consumption due to sequential accesses. Setting and to 100 effectively disables the sequential
access page stealing feature.
What Are the Side Effects of Raising the Value?
Setting the tunable too high may yield poor performance for large sequential I/O's for large files (larger than physical memory size). and
should be tuned appropriately for the anticipated workload.
When Should the Value of This Tunable Be Lowered?
When you wish to limit file cache consumption due to sequential accesses. Setting and to 0 forces sequential access page stealing to
always occur.
What Are the Side Effects of Lowering the Value?
Could cause more pageouts to occur in an attempt to limit the file cache consumption.
What Other Tunable Values Should Be Changed at the Same Time?
and should be changed at the same time.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
SEE ALSO
fcache_seqlimit_file(5).
Tunable Kernel Parameters fcache_seqlimit_system(5)