Bug 765299 (GLUSTER-3567) - need more details of memory usage patterns in statedump
Summary: need more details of memory usage patterns in statedump
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-3567
Product: GlusterFS
Classification: Community
Component: logging
Version: mainline
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-16 06:13 UTC by Amar Tumballi
Modified: 2015-12-01 16:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Amar Tumballi 2011-09-16 06:13:44 UTC 
We are missing details about 'mem-pool' usage, and also, after bringing in variable-sized iobufs bug 762514 is no more valid (ie, we do need passive iobufs to get details of how it was used).

in each type also add how many times each type of variable was allocated. This helps us to understand which of the types can be using 'iobuf' or 'mempool'.
Comment 1 Anand Avati 2011-09-22 08:33:43 UTC 
CHANGE: http://review.gluster.com/376 (* iobuf: add variable to keep count of total number of allocations) merged in master by Vijay Bellur (vijay)
Comment 2 Anand Avati 2011-09-23 05:22:59 UTC 
CHANGE: http://review.gluster.com/491 (* with this, it helps to find out most of the leaks in the process) merged in master by Vijay Bellur (vijay)
Note You need to log in before you can comment on or make changes to this bug.