Antoine Pitrou <pit...@free.fr> added the comment:

Very high-level comments on your patch:

- why an empty "dtrace" module?

- I'm worried that you're adding lots of delicate code inside critical core 
functions. Perhaps most of it can be factored out in separate functions living 
in another (dtrace-specific) C file? I don't think we really want to maintain 
some asm("nop") in the GC module, and I'm not even talking about the madness in 
ceval.c.

- instead of generating code data (line numbers etc.) up front, why not 
generate and cache it lazily? that way, it would only be generated when the 
probes are really used (IIUC)

For higher-level benchmarks, I suggest you take a look at 
http://hg.python.org/benchmarks/

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue13405>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to