Sponsored Content
Full Discussion: Paging space
Operating Systems AIX Paging space Post 302416221 by shockneck on Sunday 25th of April 2010 04:14:20 PM
Old 04-25-2010
Quote:
Originally Posted by Scrutinizer
Hi, paging space should most certainly be mirrored.
You are right. The paging space contains program code that does not fit into RAM. Imagine what would happen if the single disk that contains the paging space fails. The effect would be as if you lose a memory chip. Therefore you definitely mirror your paging space if you mirror your rootvg already.
Quote:
Originally Posted by Scrutinizer
IMO mirroring paging space will not impact performance very much and may even improve performance in some cases.
I do not know what your AIX background is but as you answer questions about AIX memory management you must be experienced. However, I think here you took the wrong turn.
If you use dedicated SCSI disks for you rootvg those disks usually deliver about 150 to 300 IOPS. With those the disks turn to 100% busy and from then on your GHz Power CPUs (with currently around 4.000.000.000 cycles per second) sit there idle. Improve performance? Well... probably in a micropartion environment you manage to completely deactivate the CPU cycles for the server paging and transfering the cycles to other LPAR - these might then indeed improve their performance. Smilie

If you use SAN disks for the rootvg you may get a higher number of IOPS but never get close to anything taking place in RAM. More likely using the SAN that way will interfere with other servers that use the same physical disks in the underlying SAN boxes. So again the impact on performance is huge.

Therefore you do not want the paging space being used. Mind that I do not say that there must be no paging space. But paging space is meant as a last resort in case an unexpected request for more memory appears. An AIX administrator will always strieve for calculating how much memory the server's applications need so that it runs in RAM and make that amount of RAM available. An AIX server that uses paging space all the time is not sized correctly.
 

10 More Discussions You Might Find Interesting

1. AIX

swap space / paging space

how do you get the paging space reduced without rebooting the machine ? the os is aix (2 Replies)
Discussion started by: aaronh
2 Replies

2. AIX

Paging Space per process

This is my first post, and I am new to the UNIX world. Hopefully this question won't be too lame. I know that I can use topas to see the paging space used by some processes. I would like to script something that can add up the paging space used by process owned by or associated with an... (1 Reply)
Discussion started by: alntht
1 Replies

3. AIX

How to distribute paging space among multiple PV

Greetings I have an older box (H50) that has it's paging space setup the following way: $ lsps -a Page Space Physical Volume Volume Group Size %Used Active Auto Type paging00 hdisk0 rootvg 224MB 1 yes yes lv hd6 hdisk0 ... (4 Replies)
Discussion started by: outtacontrol
4 Replies

4. AIX

paging space out high

Hello, we have a problem with lpar with AIX 5.3, the issue is that has high level paging space with: _sqlsrv2 and its incremented continously (1 Reply)
Discussion started by: lo-lp-kl
1 Replies

5. UNIX for Dummies Questions & Answers

Paging space definition

sorry for this silly question, I am new to UNIX, what is meant by paging space and what is its purpose? what is also meant by hd6 paging space? (2 Replies)
Discussion started by: docaia
2 Replies

6. AIX

Paging space

Hello everyone I have 4g of paging space in my rootvg disk I´m going to reduce them to 1gb in my rootvg disk and add 3gb of paging space on my san disk. My rootvg disk is mirror. My question is I can do this on line ? and I can do with the mirror ? or I need to unmirror first my... (2 Replies)
Discussion started by: lo-lp-kl
2 Replies

7. AIX

reduce used paging space

Hi I have used gzip on AIX and the used paging space has jumped from 7% to 20%. The gzip process is finished since a long time. But the used paging space is still the same. How to release this space ? (1 Reply)
Discussion started by: bfarah
1 Replies

8. AIX

paging space

Hello everyone I have a doubt about how many paging space can have in the same disk. lsps -a Page Space Physical Volume Volume Group Size %Used Active Auto Type paging00 hdisk0 rootvg 3072MB 1 yes yes lv hd6 hdisk0 ... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies

9. AIX

LV without Paging Space

Hello dear friends, We have VG filevg which consists of 2 PVs when I rechecked the VG there is no Pagingspace LV.. The VG is usually Highly loaded because much reads and writes.. Is this a must to create Paging space on the specified LV? (2 Replies)
Discussion started by: Vit0_Corleone
2 Replies

10. AIX

No Paging Space Available

Whilst perfoming some tests on lvm's I managed to crash our test box. No real problem as it is only used by our tech team. however I would like to know why this was actually caused as the task being performed at the time was one which I though would not have any impact. Using dd I was... (5 Replies)
Discussion started by: tugger
5 Replies
desfree_pct(5)							File Formats Manual						    desfree_pct(5)

NAME
desfree_pct - sets the lower bound before paging daemon starts stealing pages, specified as a percentage of available physical memory VALUES
Failsafe Default Allowed values Must not be greater than (see lotsfree_pct(5)). DESCRIPTION
is a tunable parameter to set the lower bound before the paging daemon start stealing pages. It is specified as a percentage of physical memory available after boot. must be a positive integer between 0 and 30 and must be equal to or less than (see lotsfree_pct(5)). Trying to set higher than results in The paging daemon in HP-UX acts on a "two hand" model. The daemon runs at least once a second, with one part marking pages of virtual address space as "unused". If the page is referenced before this "aging" hand returns, it will be marked as "used" again. Another section of the daemon, the "steal" hand follows the age hand (the distance between them varies in a well bounded range) and processes pages which are still marked "unused", since needed or frequently accessed pages would have a high likelihood of being referenced in the gap between the hands. Exactly how the steal hand treats the pages still marked as "unused" depends on the comparison of free system physical memory and three paging parameters: and Between and is a periodically re-calculated and, hence floating, threshold known as Thus and are the upper and lower bounds between which moves. is an expression of how much the system maintains, expressed in percentage terms (percentage of physical memory available after boot). o If is greater than the system's memory availability is in good shape. The steal hand does nothing as a lot of memory is still available on the system, so there is no need to "steal' a page that might be needed soon. o In the more common case, when is lower than (but higher than the steal hand will begin to steal pages that have remained unreferenced from when the age hand last marked them. "Stealing" a page refers to the process of freeing the page from being allocated for a partic- ular virtual page and making it available for general allocation again. If falls below but is still more than memory availability is still in reasonable shape, but the paging daemon begins stealing pages more aggressively, including putting lower priority processes to sleep to free up their memory. o When is less than free memory in the system is getting more critical; the paging daemon begin deactivating low priority processes, in other words, swapping out pages to the swap device. Since the exact memory topography varies widely across supported platforms, the paging parameters and are tunable to allow for cases where the default values are insufficient, or where the system administrator requires more control over the actions of the paging daemon. In general, however, the automatic calculation performed by default should suffice for most systems. is a system calculated value. Who Is Expected to Change This Tunable? Anyone with super-user privileges. Restrictions on Changing Changes to this tunable take effect immediately. When Should the Value of This Tunable Be Raised? This tunable should be raised on systems where system memory is critical for short-term, high priority processes, but is being held by low- priority, long running processes. For example, when one web server is forking off per-connection threads while 50 RCS clients run in the background. Increasing (and hence would raise the likelihood of the low-priority processes being put to sleep, allowing the high-priority processes a chance to acquire the pages that were previously allocated to the former. What are the Side Effects of Raising the Value? As increases, more low priority processes might be forced to sleep. Depending on what these processes are actually doing, this may not be the right approach. When Should the Value of This Tunable Be Lowered? Raising too high can impair performance of lower priority processes as previously described. In addition, raising and increases system overhead (it takes time to swap a page to disk), and should be weighed carefully against the need or desire to keep a large pool of physical memory unused. Some free memory is essential, a moderate amount is probably good, a lot of free memory just sitting idle is a waste. If the available physical memory on the machine seems generous and heavy swapping is occurring, lowering and/or will increase memory usage but decrease swapping overhead. What are the Side Effects of Lowering the Value? More physical memory will be in use before processes are put to sleep to try to reclaim their frames. What Other Tunable Values Should Be Changed at the Same Time? should be considered when modifying for reasons previously described above. acts as a firm upper bound to so attempting to set above is meaningless and will result in an error. See lotsfree_pct(5). Notes Starting with HP-UX 11i Version 2, HP recommends the use of to specify the lower bound for the paging daemon. ERRORS
Memory resource management infrastructure is busy. Please try later. Attempting to set above An invalid value is entered that is not an integer between 0 and 30, such as an negative number. 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
lotsfree_pct(5). Tunable Kernel Parameters desfree_pct(5)
All times are GMT -4. The time now is 05:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy