You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2017/07/12 23:23:00 UTC
[jira] [Created] (IMPALA-5658) Report details of process memory
maps via metrics
Tim Armstrong created IMPALA-5658:
-------------------------------------
Summary: Report details of process memory maps via metrics
Key: IMPALA-5658
URL: https://issues.apache.org/jira/browse/IMPALA-5658
Project: IMPALA
Issue Type: Improvement
Components: Backend
Affects Versions: Impala 2.10.0
Reporter: Tim Armstrong
Assignee: Tim Armstrong
To help understand the details of process memory consumption, it would be great to have metrics that answered questions like:
* How many anonymous huge pages are allocated?
* How many memory maps is the process using?
* What is the RSS of the process?
* What is the virtual memory consumption of the process?
It looks like /proc/<pid>/smaps is the documented interface for this: https://www.kernel.org/doc/Documentation/filesystems/proc.txt
I'm thinking that maybe we could have the memory maintenance thread periodically scrape /proc/<pid>/smaps and update a set of metrics like:
* Number of mappings
* Total virtual address space
* Total RSS
* Total bytes of anon huge pages
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)