There is a abrupt memory rise observed for a process on solaris.
When the process is started the memory is around 268 MB and is stable for a day. Then suddenly the memory increased to 4364 MB.
Below is the pmap -xs output for the process (only for heap)
Can anyone please help me in understanding the reason of sudden allocation of heap as huge as 4190208 (4 GB). What is the significance of empty RSS and Anon as observed for adress space
Hello all
'top' command shows the top 15 processes in terms of CPU usage. Is there any other command in UNIX ,that will show the top processes in terms of memory usage ? or is there a command, that will give me the memory usage of a particular process ,if I pass the process id as a... (3 Replies)
On AIX 5.3 host, the lvm_queryvg call does not work properly and results in a sudden memory rise. This is happening on one particular host and the call works fine on another host.
Is this a known issue and is there any patch available for this? (0 Replies)
Hello all,
I need a positive reply from you.
I want to copy the user-process-heap to the kernel space memory.
For that, I wrote the following code but it does not copy.
---------------- code --------------
unsigned long length_of_heap_vma = < length of vma pointing to process-heap > ;
void *... (2 Replies)
Hi
I have one Java application installed in my Solaris system. Is there a way to find out the heap memory allocated size/used size/free size for the particular Java process?
If anyone knows the command, please let me know. Even I appreciate if I have any scripts to find out the same.
... (0 Replies)
Can someone please help me with a script that will help in identifying the CPU & memory usage by a process name, rather than a process id.This is to primarily analyze the consumption of resources, for performance tweaking.
G (4 Replies)
Hi Experts,
Our servers running Solaris 10 with SAP Application. The memory utilization always >90%, but the process on SAP is too less even nothing.
Why memory utilization on solaris always looks high?
I have statement about memory on solaris, is this true:
Memory in solaris is used for... (4 Replies)
Hi,
This morning there was an app that caused a sudden spike in I/O and memory usage in the server. We found the reason for the I/O, however the memory spike was something new, as it had never happened before.
I figured out what caused the memory spike, however, how do I investigate why... (6 Replies)
Discussion started by: anaigini45
6 Replies
LEARN ABOUT PHP
malloc_trim
MALLOC_TRIM(3) Linux Programmer's Manual MALLOC_TRIM(3)NAME
malloc_trim - release free memory from the top of the heap
SYNOPSIS
#include <malloc.h>
int malloc_trim(size_t pad);
DESCRIPTION
The malloc_trim() function attempts to release free memory at the top of the heap (by calling sbrk(2) with a suitable argument).
The pad argument specifies the amount of free space to leave untrimmed at the top of the heap. If this argument is 0, only the minimum
amount of memory is maintained at the top of the heap (i.e., one page or less). A nonzero argument can be used to maintain some trailing
space at the top of the heap in order to allow future allocations to be made without having to extend the heap with sbrk(2).
RETURN VALUE
The malloc_trim() function returns 1 if memory was actually released back to the system, or 0 if it was not possible to release any memory.
ERRORS
No errors are defined.
ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7).
+--------------+---------------+---------+
|Interface | Attribute | Value |
+--------------+---------------+---------+
|malloc_trim() | Thread safety | MT-Safe |
+--------------+---------------+---------+
CONFORMING TO
This function is a GNU extension.
NOTES
This function is automatically called by free(3) in certain circumstances; see the discussion of M_TOP_PAD and M_TRIM_THRESHOLD in mal-
lopt(3).
This function cannot release free memory located at places other than the top of the heap.
This function releases only memory in the main arena.
SEE ALSO sbrk(2), malloc(3), mallopt(3)COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
Linux 2017-09-15 MALLOC_TRIM(3)
04-11-2014
