Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide more accurate memory statistics on Linux by using /proc/smaps #96

Closed
giampaolo opened this issue May 23, 2014 · 5 comments
Closed

Comments

@giampaolo
Copy link
Owner

From g.rodola on June 15, 2010 14:22:54

This article explains the problem: 
http://bmaurer.blogspot.com/2006/03/memory-usage-with-smaps.html 
Accurate memory usage statistics using smaps are also being used in 
Unladen Swallow benchmarks: http://www.python.org/dev/peps/pep-3146/#memory-usage

Original issue: http://code.google.com/p/psutil/issues/detail?id=96

@giampaolo giampaolo self-assigned this May 23, 2014
@giampaolo
Copy link
Owner Author

From jlo...@gmail.com on June 17, 2010 14:31:24

From the first link: 

> The vmsize and total rss size are the statistics that everyone is used to. The rss size is split into 
> “private” and “shared”. The private rss is what could be best called the process' memory usage.

This could end up being confusing for people used to the 'standard' 
definitions of RSS, so we may wish to consider a separate attribute 
for 'private' vs 'shared' RSS so as not to confuse people when they compare our values to top/ps or other statistics.

@giampaolo
Copy link
Owner Author

From g.rodola on October 26, 2010 05:55:55

Postponing for 0.2.1 release.

Labels: Milestone-0.2.1

@giampaolo
Copy link
Owner Author

From g.rodola on February 28, 2011 13:54:45

Labels: -Milestone-0.2.1

@giampaolo
Copy link
Owner Author

From g.rodola on October 22, 2011 04:46:06

Status: WaitingForReview

@giampaolo
Copy link
Owner Author

From g.rodola on June 03, 2012 15:44:01

Closing out as a duplicate because this is going to be addressed by new get_memory_maps() methods ( issue 260 ).

Status: Duplicate
Mergedinto: 260

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant