- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: SWAP 100% FULL
Operating System - HP-UX
1753470
Members
5156
Online
108794
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-06-2005 09:27 PM
тАО02-06-2005 09:27 PM
Re: SWAP 100% FULL
Hi,
If the system is running full over time here is a memory leak in one of your applications.
Quite often it is in a self made application, since Off the shelf applications should be tested against memory leaks. ;-)
These tools can be used to measure the amount of swapping in your system.
iostat (for the swap volume)
vmstat (for swap stats)
man iostat or man vmstat give you the options.
Regards,
Bob
If the system is running full over time here is a memory leak in one of your applications.
Quite often it is in a self made application, since Off the shelf applications should be tested against memory leaks. ;-)
These tools can be used to measure the amount of swapping in your system.
iostat (for the swap volume)
vmstat (for swap stats)
man iostat or man vmstat give you the options.
Regards,
Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-06-2005 09:49 PM
тАО02-06-2005 09:49 PM
Re: SWAP 100% FULL
Ok, here is my sysdef :
NAME VALUE BOOT MIN-MAX UNITS FLAGS
acctresume 4 - -100-100 -
acctsuspend 2 - -100-100 -
allocate_fs_swapmap 0 - - -
bufpages 131072 - 0- Pages -
create_fastlinks 0 - - -
dbc_max_pct 50 - - -
dbc_min_pct 5 - - -
default_disk_ir 0 - - -
dskless_node 0 - 0-1 -
eisa_io_estimate 768 - - -
eqmemsize 46 - - -
file_pad 10 - 0- -
fs_async 0 - 0-1 -
hpux_aes_override 0 - - -
maxdsiz 65536 - 0-503866 Pages -
maxdsiz_64bit 262144 - 1024-1073479679 Pages -
maxfiles 2048 - 30-2048 -
maxfiles_lim 2048 - 30-2048 -
maxssiz 2048 - 0-98048 Pages -
maxssiz_64bit 2048 - 4-262144 Pages -
maxswapchunks 8192 - 1-16384 -
maxtsiz 16384 - 0-503859 Pages -
maxtsiz_64bit 262144 - 1024-1073741823 Pages -
maxuprc 256 - 3- -
maxvgs 10 - - -
msgmap 39 - 3- -
nbuf 68646 - 0- -
ncallout 2064 - 6- -
ncdnode 150 - - -
ndilbuffers 30 - 1- -
netisr_priority -1 - -1-127 -
netmemmax 0 - - -
nfile 2302 - 14- -
nflocks 512 - 2- -
ninode 1340 - 14- -
no_lvm_disks 0 - - -
nproc 1044 - 10- -
npty 60 - 1- -
nstrpty 60 - - -
nswapdev 10 - 1-25 -
nswapfs 10 - 1-25 -
public_shlibs 1 - - -
remote_nfs_swap 0 - - -
rtsched_numpri 32 - - -
sema 0 - 0-1 -
semmap 63 - 4- -
shmem 0 - 0-1 -
shmmni 200 - 3-1024 -
streampipes 0 - 0- -
swapmem_on 1 - - -
swchunk 2048 - 2048-16384 kBytes -
timeslice 10 - -1-2147483648 Ticks -
unlockable_mem 32768 - 0- Pages -
NAME VALUE BOOT MIN-MAX UNITS FLAGS
acctresume 4 - -100-100 -
acctsuspend 2 - -100-100 -
allocate_fs_swapmap 0 - - -
bufpages 131072 - 0- Pages -
create_fastlinks 0 - - -
dbc_max_pct 50 - - -
dbc_min_pct 5 - - -
default_disk_ir 0 - - -
dskless_node 0 - 0-1 -
eisa_io_estimate 768 - - -
eqmemsize 46 - - -
file_pad 10 - 0- -
fs_async 0 - 0-1 -
hpux_aes_override 0 - - -
maxdsiz 65536 - 0-503866 Pages -
maxdsiz_64bit 262144 - 1024-1073479679 Pages -
maxfiles 2048 - 30-2048 -
maxfiles_lim 2048 - 30-2048 -
maxssiz 2048 - 0-98048 Pages -
maxssiz_64bit 2048 - 4-262144 Pages -
maxswapchunks 8192 - 1-16384 -
maxtsiz 16384 - 0-503859 Pages -
maxtsiz_64bit 262144 - 1024-1073741823 Pages -
maxuprc 256 - 3- -
maxvgs 10 - - -
msgmap 39 - 3- -
nbuf 68646 - 0- -
ncallout 2064 - 6- -
ncdnode 150 - - -
ndilbuffers 30 - 1- -
netisr_priority -1 - -1-127 -
netmemmax 0 - - -
nfile 2302 - 14- -
nflocks 512 - 2- -
ninode 1340 - 14- -
no_lvm_disks 0 - - -
nproc 1044 - 10- -
npty 60 - 1- -
nstrpty 60 - - -
nswapdev 10 - 1-25 -
nswapfs 10 - 1-25 -
public_shlibs 1 - - -
remote_nfs_swap 0 - - -
rtsched_numpri 32 - - -
sema 0 - 0-1 -
semmap 63 - 4- -
shmem 0 - 0-1 -
shmmni 200 - 3-1024 -
streampipes 0 - 0- -
swapmem_on 1 - - -
swchunk 2048 - 2048-16384 kBytes -
timeslice 10 - -1-2147483648 Ticks -
unlockable_mem 32768 - 0- Pages -
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-06-2005 09:56 PM
тАО02-06-2005 09:56 PM
Solution
hi,
see on the line.
dbc_max_pct 50 - - -
dbc_max_pct 50 means it can take up to 50% of your physical memory for buffer cache.for your system(8GB) it can be up to 4GB which is a waste.
memory of 600-800MB willbe much enough for buffer cache.
reduce the value of dbc_max_pct parameter in kernel to a value of 10 . it will free a lot of space in your system.
note: it is a ststic parameter.you must have to rebuild the kernel for changing it.use sam.it is safe.
regds,
see on the line.
dbc_max_pct 50 - - -
dbc_max_pct 50 means it can take up to 50% of your physical memory for buffer cache.for your system(8GB) it can be up to 4GB which is a waste.
memory of 600-800MB willbe much enough for buffer cache.
reduce the value of dbc_max_pct parameter in kernel to a value of 10 . it will free a lot of space in your system.
note: it is a ststic parameter.you must have to rebuild the kernel for changing it.use sam.it is safe.
regds,
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP