This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients loewis, nadeem.vawda, neologix, pitrou, python-dev, vstinner
Date 2012-02-26.12:19:33
SpamBayes Score 0.0003182479
Marked as misclassified No
Message-id <CAH_1eM0-Mr+Jeh_7NSJArTui4mBcpgzQXHwMdtiE6uNuR03uPw@mail.gmail.com>
In-reply-to <1330257351.04.0.329686909156.issue14107@psf.upfronthosting.co.za>
Content
> 1. IIUC, the goal of the watchdog thread is to collect memory
> consumption in a timely manner: that's now the case, but since the
> information is printed in a standard thread, it doesn't bring any improvement (because it can be delayed for arbitrarily long), or am I
> missing something?

Scratch that. It does bring an improvement for a post facto analysis
(I thought at first it was used in a pseudo-realtime way).
History
Date User Action Args
2012-02-26 12:19:34neologixsetrecipients: + neologix, loewis, pitrou, vstinner, nadeem.vawda, python-dev
2012-02-26 12:19:33neologixlinkissue14107 messages
2012-02-26 12:19:33neologixcreate