Message168125
| Author |
pitrou |
| Recipients |
flox, hynek, ned.deily, pitrou, r.david.murray, ronaldoussoren |
| Date |
2012年08月13日.16:39:31 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1344875802.3407.3.camel@localhost.localdomain> |
| In-reply-to |
<1344874253.04.0.318855235524.issue15635@psf.upfronthosting.co.za> |
| Content |
> > All of this clearly points towards malloc not releasing allocated memory to the system.
> > This is perfectly fine and not a bug in either Python or the system.
>
> So it means there's no reliable way to measure the memory consumption of the program.
What it means is that "memory consumption" itself is a bit ill-defined.
"ps", "top" and friends will tell you the amount of memory (physical or
virtual) currently assigned by the OS to the process. It doesn't tell
you whether the memory is "actually" in use by the program.
Note that, in Python 3.3, sys._debugmallocstats() gives you
fined-grained information about the object allocator. This excludes any
blocks bigger than 512 bytes, though, since those are requested directly
using malloc() and free(). |
|