➜

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 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.09:57:48
SpamBayes Score 1.004869e-06
Marked as misclassified No
Message-id <CAH_1eM3K2HvO6qM+gps95Am4==cs4HK=rdfAo01tPybXhZ7yNg@mail.gmail.com>
In-reply-to <1323581916.04.0.448885739763.issue13405@psf.upfronthosting.co.za>
Content 
> Alan, I would open a new issue tracking this one and posting a patch there, if I were you.
>
> Previous DTRACE attempts failed because trying to make everybody happy. I don't want to repeat the mistake.
>

Sorry, but I'm -1.
I don't feel comfortable with adding a such amount of intrusive code,
which will have to be maintained as the interpreter evolves, to add
probes just for Solaris derivatives, which is, with all due respect,
really a niche platform. So If we merge this, this should at least
support SystemTap upfront.

> In fact this instrumentalization can be used to locate hotspots in python interpreter and maybe improve overall performance.

You can already go a really long way with just strace and oprofile, I
don't really but the performance optimization argument.

Also, I must admit I'm quite skeptical about the real benefit of
explicit probes for user-land, especially for CPython which isn't used
for performance-critical systems...
History
Date User Action Args
2011-12-12 09:57:49neologixsetrecipients: + neologix, loewis, rhettinger, jcea, ronaldoussoren, belopolsky, pitrou, wsanchez, movement, techtonik, serverhorror, glyph, laca, twleung, jbaker, robert.kern, sirg3, danchr, dhduvall, dmalcolm, mjw, Garen, lasizoillo, fche, hazmat, jmcp, scox
2011-12-12 09:57:49neologixlinkissue13405 messages
2011-12-12 09:57:48neologixcreate