Sponsored Content
Full Discussion: The immortal aioserver
Operating Systems AIX The immortal aioserver Post 302958328 by Linusolaradm1 on Wednesday 21st of October 2015 10:24:12 AM
Old 10-21-2015
Already play with ioo,i set for test 1 to posix_aio_server_inactivity
and
aio_server_inactivity
But nothing change

---------- Post updated at 09:24 AM ---------- Previous update was at 09:23 AM ----------

Quote:
Originally Posted by zaxxon
Please issue lsof +D /oracle and show the output in code tags, thanks.

And do not try to kill those aioservers. Once started they will stay active, even if not needed. They have a starting amount and a max amount. If the system needs more of them than the starting amount, it spawns new ones until max is reached but, as said, they stay in the process list and do not terminate. If not needed, they just idle and do not really eat performance.
lsof +D report nothing
 

2 More Discussions You Might Find Interesting

1. AIX

AIOServer process question

Hi I've been trying to learn a bit more about AIOServer processes and how my company administers them, one question i have is, while checking, most of my servers show a memory overhead of about 448 k per aioserver process (nmon -A) however i have found a few with figures of 67 or 56k. Most... (0 Replies)
Discussion started by: philib
0 Replies

2. AIX

aioserver query

Hi Gurus, What is the recommended value for aioserver in aix 5.3 current value is 16384 And used is ps -k|wc -l 4768 We usauslly get issues like slow server performance and query waiting time more etc. Regards newaix (2 Replies)
Discussion started by: newaix
2 Replies
MEMSTAT(1)						     Linux Programmer's Manual							MEMSTAT(1)

NAME
memstat - Identify what's using up virtual memory. SYNOPSIS
memstat [-w][-p PID] DESCRIPTION
memstat lists all accessible processes, executables, and shared libraries that are using up virtual memory. To get a complete list memstat has to be run as root to be able to access the data of all running processes. First, the processes are listed. An amount of memory is shown along with a process ID and the name of the executable which the process is running. The amount of memory shown does not include shared memory: it only includes memory which is private to that process. So, if a process is using a shared library like libc, the memory used to hold that library is not included. The memory used to hold the exe- cutable's text-segment is also not included, since that too is shareable. After the processes, the shared objects are listed. The amount of memory is shown along with the filename of the shared object, followed by a list of the processes using the shared object. The memory is listed as the total amount of memory allocated to this object throughout the whole namespace. In brackets also the amount that is really shared is listed. Finally, a grand total is shown. Note that this program shows the amount of virtual (not real) memory used by the various items. memstat gets its input from the /proc filesystem. This must be compiled into your kernel and mounted for memstat to work. The pathnames shown next to the shared objects are determined by scanning the disk. memstat uses a configuration file, /etc/memstat.conf, to determine which directories to scan. This file should include all the major bin and lib directories in your system, as well as the /dev directory. If you run an executable which is not in one of these directories, it will be listed by memstat as ``[0dev]:<inode>''. Options The -w switch causes a wide printout: lines are not truncated at 80 columns. The -p switch causes memstat to only print data gathered from looking at the process with the gicen PID. NOTES
These reports are intended to help identify programs that are using an excessive amount of memory, and to reduce overall memory waste. FILES
/etc/memstat.conf /proc/*/maps SEE ALSO
ps(1), top(1), free(1), vmstat(8), lsof(8), /usr/share/doc/memstat/memstat-tutorial.txt.gz BUGS
memstat ignores all devices that just map main memory, though this may cause memstat to ignore some memory usage. Memory used by the kernel itself is not listed. AUTHOR
Originally written by Joshua Yelon <jyelon@uiuc.edu> and patched by Bernd Eckenfels <ecki@debian.org>. Taken over and rewritten by Michael Meskes <meskes@debian.org>. Debian 01 November 1998 MEMSTAT(1)
All times are GMT -4. The time now is 08:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy