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:
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 DEBIAN
ns_calloc
Ns_Alloc(3aolserver) AOLserver Library Procedures Ns_Alloc(3aolserver)__________________________________________________________________________________________________________________________________________________NAME
ns_calloc, ns_free, ns_malloc, ns_realloc - Memory allocation functions
SYNOPSIS
#include "ns.h"
void *
ns_calloc(size_t num, size_t esize)
void
ns_free(void *ptr)
void *
ns_malloc(size_t size)
void *
ns_realloc(void *ptr, size_t size)
_________________________________________________________________DESCRIPTION
The AOLserver memory storage allocation code was moved into Tcl core beginning with Tcl 8.4.0. Starting with AOLserver 3.5, these memory
allocation functions are wrappers that call Tcl_Alloc and Tcl_Free. Earlier versions of AOLserver used this fast memory storage allocator
internally, or the platform's memory allocator depending on how you configured it.
The actual amount of memory allocated or freed will be different from the requested amount. This is because the fast memory allocation
code pools memory into chunks and manages that memory internally. In addition, the Tcl distribution may be compiled to allocate even more
memory which is used internally for diagnostic reasons. Using ns_free to free memory created by routines other than ns_malloc, ns_realloc
and ns_calloc will almost certainly result in segmentation faults or undefined behavior.
The lowercase and mixed-case versions are identical; the lowercase versions are preferred.
ns_calloc(num, esize)
Allocates a block of memory that is num * esize large, zeros it, and returns a pointer to the beginning of the memory block or NULL
if the operation fails.
ns_free(ptr)
ns_free() frees the memory space pointed to by ptr. This pointer must have been created with a previous call to ns_malloc(), ns_cal-
loc() or ns_realloc(). If ptr is NULL, no operation is performed. ns_free() returns no value.
ns_malloc(size)
ns_malloc() allocates size bytes and returns a pointer to the allocated memory. The memory is not cleared. The value returned is a
pointer to the allocated memory or NULL if the request fails. The memory must be freed by ns_free.
ns_realloc(ptr, size)
ns_realloc changes the size of the memory block pointed to by ptr to size bytes. The contents will be unchanged to the minimum of
the old and new sizes. Newly allocated memory will be uninitialized. If ptr is NULL, the call is equivalent to ns_malloc(size); if
size is equal to zero, the call is equivalent to ns_free(ptr). Unless ptr is NULL, it must have been returned by an earlier call to
ns_malloc(), ns_calloc() or ns_realloc().
SEE ALSO Tcl_Alloc(3), Tcl_Free(3)KEYWORDS
memory, allocation
AOLserver 4.0 Ns_Alloc(3aolserver)