In AIX 6.1 lru_file_repage is set to 0 by default. Wouldn't setting this option to 1 cause heavier paging? As you can see there are almost all lruable pages so i guess this would have performance impact. Also restricted options like lru_file_repage are not mentioned in manual pages.
About the kernel using file memory, file memory isn't only used by kernel, is it correct? Currently there is more file memory than kernel memory in use:
Code:
===========================================================================
Memory accounting summary | 4K Pages | Megabytes
----------------------------------------------------|----------|-----------
Total memory in system | 16842752 | 65792.00
Total memory in use | 13098163 | 51164.69
Kernel identified memory (segids,wlm_hw_pages) | 4051924 | 15827.82
Kernel un-identified memory | 18006 | 70.33
Fork tree pages | 0 | 0.00
Large Page Pool free pages | 0 | 0.00
Huge Page Pool free pages | 0 | 0.00
User private memory | 1379905 | 5390.25
User shared memory | 1127620 | 4404.76
User shared library text memory | 141072 | 551.06
Text/Executable code memory in use | 8880 | 34.68
Text/Executable code memory not in use | 279924 | 1093.45
File memory | 5696733 | 22252.86
User un-identifed memory | 394099 | 1539.44
---------------------- | |
Total accounted in-use | 13098163 | 51164.69
Free memory | 3744589 | 14627.30
---------------------- | |
Total identified (total ident.+free) | 16430647 | 64182.21
Total unidentified (kernel+user w/ segids) | 412105 | 1609.78
---------------------- | |
Total accounted | 16842752 | 65792.00
Total unaccounted | 1277893 | 4991.76
it's being purged once in a while (can't post URL, because i don't have 5 posts yet, so i might add it in the future posts )
i will explore the ipcs to see if i find something useful, thanks for steering
Hello,
I'm using a unix server (HP rp2450) which has : 2 Go RAM memory and 4 Go swap.
Here is the result of vmstat -n command :
$ vmstat -n
VM
memory page faults
avm free re at pi po fr de sr in sy ... (5 Replies)
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)
Hi
I am trying to investigate a disk performance issue, and we are not seem to be hitting the right direction in our analysis.
This is a FC disk running on USP1000 HDS system. The application is an IO intensive application, but our opinion is that it is not performing due to perceived disk... (1 Reply)
Dear friends. can anybody suggest me what to be considered in order to achieve maximum performance of AIX on which DB2 will be installed
Thanks is advance :) (1 Reply)
Dears i want to have a clear view about this tuning parameters and what they related to FS or Oracle , and how to figure the percentage of them .
maxperm%
maxclient%
v_pinshm = 1
lgpg_regions = 0
lpgp_size = 0 (3 Replies)
For some reason, my AIX 5.2 box has become slow in accepting telnet requests from others boxes. Windows, times out the connection, whereas, Unix it will wait for the AIX to display the login. I connect and it respawns back and says connected, but then sits and wait for what seems forever to get the... (5 Replies)
Hi,
we've a gigabit Ethernet adapter. And we wanted to improve the performance by tuning network parameters. so' as per IBM info center,
http://publib.boulder.ibm.com/infocenter/aix/v7r1/index.jsp?topic=%2Fcom.ibm.aix.prftungd%2Fdoc%2Fprftungd%2Fnetw_opt.htm
we tried changing the tuning... (2 Replies)
I have a IBM Power9 server coupled with a NVMe StorWize V7000 GEN3 storage, doing some benchmarks and noticing that single thread I/O (80% Read / 20% Write, common OLTP I/O profile) seems slow.
./xdisk -R0 -r80 -b 8k -M 1 -f /usr1/testing -t60 -OD -V
BS Proc AIO read% IO Flag IO/s ... (8 Replies)
Discussion started by: c3rb3rus
8 Replies
LEARN ABOUT HPUX
aio_physmem_pct
aio_physmem_pct(5) File Formats Manual aio_physmem_pct(5)NAME
aio_physmem_pct - percentage of physical memory lockable for request call-back POSIX asynchronous I/O operations
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 limit on how much system memory can be locked by the total number of POSIX asynchronous I/O operations that are in
progress at any given time.
It is important to be aware that an operation remains on the active queue and memory is not released, even if the operation is complete,
until it is properly terminated by an call for that operation.
The value of represents a percentage of system memory, and the limit it controls will adjust with Online Addition or Deletion of physical
memory (OL*), as appropriate.
Asynchronous I/O operations that use a request-and-callback mechanism for I/O must be able to lock the memory they are using. The request-
and-callback mechanism is used only if the device drivers involved support it. Memory is locked only while the I/O transfer is in
progress.
imposes a system-wide limit on lockable physical memory. A per-process lockable-memory limit can also be self-imposed by using the system
call within the application program (see setrlimit(2)).
Who Is Expected to Change This Tunable?
System administrators that run applications requiring heavy usage of POSIX AIO to file systems.
Restrictions on Changing
This tunable is dynamic. Any changes to the value of this tunable will take effect immediately without requiring system reboot.
The amount of memory that can be locked under the limit imposed by cannot exceed the total system wide lockable memory limit imposed by
The limit dictated by this tunable, is checked individually for each incoming request for file system or devices that support the
request/callback mechanism. When tuning to a lower value, the new limit will be immediately enforced for all new requests, and the tuning
will succeed even if the current usage count is higher. The usage will then gradually adjust to the new limit.
When Should the Value of This Tunable Be Raised?
On a large server it is better to increase to higher values (up to 50).
What Other Tunables Should Be Changed at the Same Time as This One?
The total amount of memory that can be locked at any given time for any reason, not just for asynchronous I/O, is controlled by the system-
wide limit Other system activity, including explicit memory locking with the and/or interfaces can also affect the amount of lockable mem-
ory at any given time.
There is no kernel parameter named but there is a parameter named that affects it. The value of is determined by subtracting the value of
from the amount of system memory available after system startup. During startup, the system displays on the system console the amount of
its lockable memory (along with available memory and physical memory). These values can be retrieved while the system is running with com-
mand.
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 kctune(1M), sam(1M), gettune(2), settune(2), aio(5), aio_return(2), dmesg(1M), mlock(2), plock(2), getrlimit(2), setrlimit(2), unlock-
able_mem(5).
Tunable Kernel Parameters aio_physmem_pct(5)