Sponsored Content
Full Discussion: Memory usage on AIX
Operating Systems AIX Memory usage on AIX Post 302238258 by aajmani on Friday 19th of September 2008 11:45:19 AM
Old 09-19-2008
Memory usage on AIX

How to check the memory usage on AIX by various processes?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Memory Usage in AIX

Hi All, I have a question, can you guys please help me by giving your valuable suggestons: I am using AIX 5L, running oracle 7 version. I need to increase the oracle memory to 40 MB more. Currently Oracle occupies 260M. I wanted to know whether I can increase the memory without any problem.... (1 Reply)
Discussion started by: kollam68
1 Replies

2. AIX

Memory Usage in AIX

Hi All, I have a question, can you guys please help me by giving your valuable suggestons: I am using AIX 5L, running oracle 7 version. I need to increase the oracle memory to 40 MB more. Currently Oracle occupies 260M. I wanted to know whether I can increase the memory without any problem.... (3 Replies)
Discussion started by: kollam68
3 Replies

3. Shell Programming and Scripting

How to calculate Memory and CPU Usage on AIX

I have written a script that will calculate CPU usage and Memory usage of a particular process on AIX Unix. I know the PID and I am using the command -- # for CPU Usage MSG_CPU_USG=`ps uax | grep ${PID} | awk {'print $3'}` #for Memory Usage MSG_MEM_USG=`ps uax | grep ${PID} | awk {'print... (0 Replies)
Discussion started by: asutoshch
0 Replies

4. AIX

High memory usage in AIX 5.1

Hi, We have AIX 5.1 machine of RAM 8 GB and paging space is 8GB. we are getting high memory usage of almost 99%.Can anybody please help in this ? Partial vmstat o/p kthr memory ----- ----------- r b avm fre 2 1 278727 1143 There is no paging issue.Becoz in... (5 Replies)
Discussion started by: jayakumarrt
5 Replies

5. HP-UX

how can I find cpu usage memory usage swap usage and logical volume usage

how can I find cpu usage memory usage swap usage and I want to know CPU usage above X% and contiue Y times and memory usage above X % and contiue Y times my final destination is monitor process logical volume usage above X % and number of Logical voluage above can I not to... (3 Replies)
Discussion started by: alert0919
3 Replies

6. AIX

How to monitor the IBM AIX server for I/O usage,memory usage,CPU usage,network..?

How to monitor the IBM AIX server for I/O usage, memory usage, CPU usage, network usage, storage usage? (3 Replies)
Discussion started by: laknar
3 Replies

7. AIX

AIX 5.3 Physical Memory usage

Hi, I have AIX 5.3TL8 two node cluster using HACMP and have 10g database using RAW devices. I am seeing gradual increase in comp% memory everyday and it reaches 100% and evicts the node, we had 4 evictions in 40days. I am pasting vmstat and vmo output, anyone seen this issue? ... (5 Replies)
Discussion started by: navin7386
5 Replies

8. AIX

AIX memory usage always high

hi, I want to ask , my AIX 6.1 is always used about 97% memory. Is this normal ? or any command can free up memory like Linux ? thanks. (1 Reply)
Discussion started by: virusxx
1 Replies

9. AIX

Memory usage in AIX server

Hi All, I have some questions regarding the performance, MEMORY/ Virtual Memory (paging /swap space) Please see the nmon-MEMORY stats from my AIX LPAR. 24 GB --> RAM 3456 MB --> Paging Space │ Memory ─────────────────────────────────────────────────────────────────────── │... (8 Replies)
Discussion started by: System Admin 77
8 Replies

10. AIX

AIX memory usage by processes

Hi, i have 2 identical web servers using AIX. I use nmon analyser to check their performance. The server A exceeds 20% memory usage for system, 5% for cache and the rest 75% for processes. While, it uses 4% of Paging Space. The server B exceeds 20% for system, 45% for cache and 35% for processes.... (24 Replies)
Discussion started by: dim
24 Replies
memsup(3erl)						     Erlang Module Definition						      memsup(3erl)

NAME
memsup - A Memory Supervisor Process DESCRIPTION
memsup is a process which supervises the memory usage for the system and for individual processes. It is part of the OS_Mon application, see os_mon(7) . Available for Unix, Windows and VxWorks. Periodically performs a memory check: * If more than a certain amount of available system memory is allocated, as reported by the underlying operating system, the alarm {sys- tem_memory_high_watermark, []} is set. * If any Erlang process Pid in the system has allocated more than a certain amount of total system memory, the alarm {process_mem- ory_high_watermark, Pid} is set. Alarms are reported to the SASL alarm handler, see alarm_handler(3erl) . To set an alarm, alarm_handler:set_alarm(Alarm) is called where Alarm is either of the alarms specified above. The alarms are cleared automatically when the alarm cause is no longer valid. The function get_memory_data() can be used to retrieve the result of the latest periodic memory check. There is also a interface to system dependent memory data, get_system_memory_data() . The result is highly dependent on the underlying operating system and the interface is targeted primarily for systems without virtual memory (e.g. VxWorks). The output on other systems is however still valid, although sparse. A call to get_system_memory_data/0 is more costly than a call to get_memory_data/0 as data is collected synchronously when this function is called. The total system memory reported under UNIX is the number of physical pages of memory times the page size, and the available memory is the number of available physical pages times the page size. This is a reasonable measure as swapping should be avoided anyway, but the task of defining total memory and available memory is difficult because of virtual memory and swapping. CONFIGURATION
The following configuration parameters can be used to change the default values for time intervals and thresholds: memory_check_interval = int()>0 : The time interval, in minutes, for the periodic memory check. The default is one minute. system_memory_high_watermark = float() : The threshold, as percentage of system memory, for how much system memory can be allocated before the corresponding alarm is set. The default is 0.80 (80%). process_memory_high_watermark = float() : The threshold, as percentage of system memory, for how much system memory can be allocated by one Erlang process before the correspond- ing alarm is set. The default is 0.05 (5%). memsup_helper_timeout = int()>0 : A timeout, in seconds, for how long the memsup process should wait for a result from a memory check. If the timeout expires, a warning message "OS_MON (memsup) timeout" is issued via error_logger and any pending, synchronous client calls will return a dummy value. Nor- mally, this situation should not occur. There have been cases on Linux, however, where the pseudo file from which system data is read is temporarily unavailable when the system is heavily loaded. The default is 30 seconds. memsup_system_only = bool() : Specifies whether the memsup process should only check system memory usage ( true ) or not. The default is false , meaning that infor- mation regarding both system memory usage and Erlang process memory usage is collected. It is recommended to set this parameter to false on systems with many concurrent processes, as each process memory check makes a tra- versal of the entire list of processes. See config(5) for information about how to change the value of configuration parameters. EXPORTS
get_memory_data() -> {Total,Allocated,Worst} Types Total = Allocated = int() Worst = {Pid, PidAllocated} | undefined Pid = pid() PidAllocated = int() Returns the result of the latest memory check, where Total is the total memory size and Allocated the allocated memory size, in bytes. Worst is the pid and number of allocated bytes of the largest Erlang process on the node. If memsup should not collect process data, that is if the configuration parameter memsup_system_only was set to true , Worst is undefined . The function is normally asynchronous in the sense that it does not invoke a memory check, but returns the latest available value. The one exception if is the function is called before a first memory check is finished, in which case it does not return a value until the memory check is finished. Returns {0,0,{pid(),0}} or {0,0,undefined} if memsup is not available, or if all memory checks so far have timed out. get_system_memory_data() -> MemDataList Types MemDataList = [{Tag, Size}] Tag = atom() Size = int() Invokes a memory check and returns the resulting, system dependent, data as a list of tagged tuples, where Tag can be one of the following: total_memory : The total amount of memory available to the Erlang emulator, allocated and free. May or may not be equal to the amount of memory configured in the system. free_memory : The amount of free memory available to the Erlang emulator for allocation. system_total_memory : The amount of memory available to the whole operating system. This may well be equal to total_memory but not necessarily. largest_free : The size of the largest contiguous free memory block available to the Erlang emulator. number_of_free : The number of free blocks available to the Erlang runtime system. This gives a fair indication of how fragmented the memory is. buffered_memory : The amount of memory the system uses for temporary storing raw disk blocks. cached_memory : The amount of memory the system uses for cached files read from disk. total_swap : The amount of total amount of memory the system has available for disk swap. free_swap : The amount of memory the system has available for disk swap. All memory sizes are presented as number of bytes . The largest_free and number_of_free tags are currently only returned on a VxWorks system. Returns the empty list [] if memsup is not available, or if the memory check times out. Note: On linux the memory available to the emulator is cached_memory and buffered_memory in addition to free_memory . get_os_wordsize() -> Wordsize Types Wordsize = 32 | 64 | unsupported_os Returns the wordsize of the current running operating system. get_check_interval() -> MS Types MS = int() Returns the time interval, in milliseconds, for the periodic memory check. set_check_interval(Minutes) -> ok Types Minutes = int()>0 Changes the time interval, given in minutes, for the periodic memory check. The change will take effect after the next memory check and is non-persistent. That is, in case of a process restart, this value is forgotten and the default value will be used. See Configuration above. get_procmem_high_watermark() -> int() Returns the threshold, in percent, for process memory allocation. set_procmem_high_watermark(Float) -> ok Changes the threshold, given as a float, for process memory allocation. The change will take effect during the next periodic memory check and is non-persistent. That is, in case of a process restart, this value is forgotten and the default value will be used. See Configuration above. get_sysmem_high_watermark() -> int() Returns the threshold, in percent, for system memory allocation. set_sysmem_high_watermark(Float) -> ok Changes the threshold, given as a float, for system memory allocation. The change will take effect during the next periodic memory check and is non-persistent. That is, in case of a process restart, this value is forgotten and the default value will be used. See Configuration above. get_helper_timeout() -> Seconds Types Seconds = int() Returns the timeout value, in seconds, for memory checks. set_helper_timeout(Seconds) -> ok Types Seconds = int() (>= 1) Changes the timeout value, given in seconds, for memory checks. The change will take effect for the next memory check and is non-persistent. That is, in the case of a process restart, this value is forgotten and the default value will be used. See Configuration above. SEE ALSO
alarm_handler(3erl) , os_mon(3erl) Ericsson AB os_mon 2.2.5 memsup(3erl)
All times are GMT -4. The time now is 05:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy