Message149312
| Author |
jcea |
| Recipients |
Garen, belopolsky, danchr, dhduvall, dmalcolm, fche, glyph, hazmat, jbaker, jcea, jmcp, laca, lasizoillo, loewis, mjw, movement, neologix, pitrou, rhettinger, robert.kern, ronaldoussoren, scox, serverhorror, sirg3, techtonik, twleung, wsanchez |
| Date |
2011年12月12日.15:23:25 |
| SpamBayes Score |
0.00033071183 |
| Marked as misclassified |
No |
| Message-id |
<1323703406.08.0.652604171579.issue13405@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
>> - Interactive interpreter invocation: 517 blocks, 95128 bytes.
>
> Note that http://bugs.python.org/issue13390 also proposes to count
> allocations in the interpreter.
The thing is, I get this data WITHOUT touching python interpreter, using a DTrace script, and when I am done and I kill the script, any malloc/free overhead will disappear. And the program keeps running...
Notice too, that the data I am showing is the extra memory I am using for the dtrace stack helper, not all python memory (if you check the dtrace script, I only contabilize "PyMem_Malloc()" when called from "PyCode_New()").
DTrace allows me to be quirurgic. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年12月12日 15:23:26 | jcea | set | recipients:
+ jcea, loewis, rhettinger, ronaldoussoren, belopolsky, pitrou, wsanchez, movement, techtonik, serverhorror, glyph, laca, twleung, jbaker, robert.kern, sirg3, danchr, dhduvall, dmalcolm, mjw, Garen, neologix, lasizoillo, fche, hazmat, jmcp, scox |
| 2011年12月12日 15:23:26 | jcea | set | messageid: <1323703406.08.0.652604171579.issue13405@psf.upfronthosting.co.za> |
| 2011年12月12日 15:23:25 | jcea | link | issue13405 messages |
| 2011年12月12日 15:23:25 | jcea | create |
|