[Python-Dev] opcode performance measurements (original) (raw)
Jeremy Hylton jeremy@alum.mit.edu
Thu, 31 Jan 2002 07:34:28 -0500
- Previous message: [Python-Dev] opcode performance measurements
- Next message: [Python-Dev] opcode performance measurements
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
"AM" == Aahz Maruch <aahz@rahul.net> writes:
AM> My suggestion WRT SET_LINENO is to encourage the use of python AM> -O and PYTHONOPTIMIZE.
Vladimir submitted a patch long ago to dynamically recompile bytecode to add/remove SET_LINENO as needed. I find that approach much more appealing, because you don't have to pay the SET_LINENO penalty just because there's some chance you'd want to connect with a debugger. A long running server process is the prime use case; it benefits from -O but may need to be debugged.
Jeremy
- Previous message: [Python-Dev] opcode performance measurements
- Next message: [Python-Dev] opcode performance measurements
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]