Sponsored Content
Operating Systems AIX AIX 6.1: Releasing Memory and Page Space Post 302491164 by zxmaus on Wednesday 26th of January 2011 08:36:17 PM
Old 01-26-2011
Hi,

let's start in the beginning - if you use paging space at all - you do not have enough memory.
Without knowing your box and what is running on it and what is normal and what is not there is no way to tell you what to do and what not to do.

So tell us something about your box. Post a vmstat -Iwt 2 10 output from a busy time (when you are filling up your pagingspace) and from a 'normal' time - so when your perl jobs do not run.

Show us an lsps -a output from a few min before your perl job is kicking in - so we know what is normal.

Show us a vmstat -s output.

There are many ways to clean up paging space if we need to - but since AIX is doing this on its own over time, you should never be in the situation of 'overflowing' memory and paging space in first instance when you do have enough memory in first instance - this will only happen when you are generally filling it up - what we do not know so far.

There are DB settings, filesystem mount options, system environment variables and finally system tunables that can help you - again we would need to know what else is on the box.

What might help you as well is to split your paging space - IBM doesnt recommend having paging spaces bigger 34 GB and it might help you with your issues of not enough buffers for pagingspaces and as well performance to split your paging area across multiple disks ...

Regards
zxmaus
 

10 More Discussions You Might Find Interesting

1. AIX

Removing page space

I having problem removing a page space.... 1. When I list the page spaces available in the system, I am getting the following messages 0516-310 : Unable to find attribute state in the Device Configuration Database. Execute synclvodm to attempt to correct the database.... (4 Replies)
Discussion started by: srnkumar
4 Replies

2. AIX

TUNING: memory page sizes

This is post number 3 in a series of unanswered "TUNING" questions. :D With AIX 5.3 TL4, the page size can vary from the original "4k". They can now be "64k" and a couple other sizes. They also do not have to all be the same. Some can remain "4k" while others are "64k" which is what seems to... (2 Replies)
Discussion started by: kah00na
2 Replies

3. Linux

ext3 file system not releasing space

Hi all i am facing a problem with ext3 file system df -h is showing 19gb is used even if there is not a single file on the mount point /dev/mapper/vg01-archive 55G 19G 33G 36% /archive_log OS == Linux cdrsvr 2.6.9-55.ELsmp #1 SMP Fri Apr 20 17:03:35 EDT 2007... (1 Reply)
Discussion started by: ajays
1 Replies

4. AIX

Lots of page faults and free memory

Hello, I've been reading your forums for quite a while and the great amount of information I find here always come in hand.This time however, I need some specific help... I have a doubt with an AIX server which I'm failing to understand as I'm new to its concept of memory management... ... (8 Replies)
Discussion started by: flpgdt
8 Replies

5. Solaris

Releasing the swap space Solaris

Hi Guys ! I have found this problem many times that the swap space (/tmp space more precisely )of my Server becomes full specially when i run a complete back up of the server . once the /tmp space is full I am not able to run simple commands as i get error like : fork no space on... (6 Replies)
Discussion started by: Paarth
6 Replies

6. Solaris

Releasing the swap space Solaris

Hi Guys ! I have found this problem many times that the swap space (/tmp space more precisely )of my Server becomes full specially when i run a complete back up of the server . once the /tmp space is full I am not able to run simple commands as i get error like : fork no space on... (4 Replies)
Discussion started by: Paarth
4 Replies

7. AIX

Increase for the Page space

Guy's This is our page space , i want some information about page space and I want the good way to how to increase the page space and what's the recommended page space that need to be configured Page Space Physical Volume Volume Group Size %Used Active Auto Type Chksum hd6 hdisk0... (8 Replies)
Discussion started by: Mr.AIX
8 Replies

8. UNIX for Dummies Questions & Answers

Page Fault + Memory

I am not sure where to post this so i will put it in the newbie section. I have set up a bog standard debain 6, LAMP environment in the cloud. The specs 1 core at 2GH 2.5gb Memory running Jommla, with about 1.6K visitors a day. I am using AppFirst (appfirst.com) to monitor the... (2 Replies)
Discussion started by: waseem
2 Replies

9. UNIX for Advanced & Expert Users

Memory Utilization swap and page scan

Hi, on AIX 6 , how to see : Memory Utilization Memory Page Scan Rate Swap Utilization Thank you. (2 Replies)
Discussion started by: big123456
2 Replies

10. AIX

AIX swap space, physical memory & cache

Hi, I am new to AIX, Can someone please help me how to know the swap space, total physical memory and system cache? We are using AIX 5.3. Thanks! (3 Replies)
Discussion started by: Phaneendra G
3 Replies
<sys/mman.h>(P) 					     POSIX Programmer's Manual						   <sys/mman.h>(P)

NAME
sys/mman.h - memory management declarations SYNOPSIS
#include <sys/mman.h> DESCRIPTION
The <sys/mman.h> header shall be supported if the implementation supports at least one of the following options: * The Memory Mapped Files option * The Shared Memory Objects option * The Process Memory Locking option * The Memory Protection option * The Typed Memory Objects option * The Synchronized Input and Output option * The Advisory Information option * The Typed Memory Objects option If one or more of the Advisory Information, Memory Mapped Files, or Shared Memory Objects options are supported, the following protection options shall be defined: PROT_READ Page can be read. PROT_WRITE Page can be written. PROT_EXEC Page can be executed. PROT_NONE Page cannot be accessed. The following flag options shall be defined: MAP_SHARED Share changes. MAP_PRIVATE Changes are private. MAP_FIXED Interpret addr exactly. The following flags shall be defined for msync(): MS_ASYNC Perform asynchronous writes. MS_SYNC Perform synchronous writes. MS_INVALIDATE Invalidate mappings. The following symbolic constants shall be defined for the mlockall() function: MCL_CURRENT Lock currently mapped pages. MCL_FUTURE Lock pages that become mapped. The symbolic constant MAP_FAILED shall be defined to indicate a failure from the mmap() function. If the Advisory Information and either the Memory Mapped Files or Shared Memory Objects options are supported, values for advice used by posix_madvise() shall be defined as follows: POSIX_MADV_NORMAL The application has no advice to give on its behavior with respect to the specified range. It is the default characteristic if no advice is given for a range of memory. POSIX_MADV_SEQUENTIAL The application expects to access the specified range sequentially from lower addresses to higher addresses. POSIX_MADV_RANDOM The application expects to access the specified range in a random order. POSIX_MADV_WILLNEED The application expects to access the specified range in the near future. POSIX_MADV_DONTNEED The application expects that it will not access the specified range in the near future. The following flags shall be defined for posix_typed_mem_open(): POSIX_TYPED_MEM_ALLOCATE Allocate on mmap(). POSIX_TYPED_MEM_ALLOCATE_CONTIG Allocate contiguously on mmap(). POSIX_TYPED_MEM_MAP_ALLOCATABLE Map on mmap(), without affecting allocatability. The mode_t, off_t, and size_t types shall be defined as described in <sys/types.h> . The <sys/mman.h> header shall define the structure posix_typed_mem_info, which includes at least the following member: size_t posix_tmi_length Maximum length which may be allocated from a typed memory object. The following shall be declared as functions and may also be defined as macros. Function prototypes shall be provided. int mlock(const void *, size_t); int mlockall(int); void *mmap(void *, size_t, int, int, int, off_t); int mprotect(void *, size_t, int); int msync(void *, size_t, int); int munlock(const void *, size_t); int munlockall(void); int munmap(void *, size_t); int posix_madvise(void *, size_t, int); int posix_mem_offset(const void *restrict, size_t, off_t *restrict, size_t *restrict, int *restrict); int posix_typed_mem_get_info(int, struct posix_typed_mem_info *); int posix_typed_mem_open(const char *, int, int); int shm_open(const char *, int, mode_t); int shm_unlink(const char *); The following sections are informative. APPLICATION USAGE
None. RATIONALE
None. FUTURE DIRECTIONS
None. SEE ALSO
<sys/types.h> , the System Interfaces volume of IEEE Std 1003.1-2001, mlock(), mlockall(), mmap(), mprotect(), msync(), munlock(), munlock- all(), munmap(), posix_mem_offset(), posix_typed_mem_get_info(), posix_typed_mem_open(), shm_open(), shm_unlink() COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol- ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html . IEEE
/The Open Group 2003 <sys/mman.h>(P)
All times are GMT -4. The time now is 01:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy