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 gvanrossum
Recipients
Date 2002-08-15.18:09:01
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=6380

> I'm surprised that there is *any* speed increase
> because I barely changed any code to make use
> this. This is very encouraging.

Don't get too excited.  Speedups and slowdowns in
the order of 1% are usually random cache effects
having to do with common portions of the VM main
loop having a cache line conflict; I've seen a
case where adding an *unreachable* printf() call
predictably changed the pystone speed by 1%.

> The localization and forced recomplication
> issues you raise are not really relevant because
> this MUST NOT be used for anything but builtin
> names and builtins are not added so
> frequently. Even standard modules should not
> declare static names.

Then why do I see all signal names in your list?
And all exception names?

> Actually, the macro PyNAME is not required any
> more and the actual symbol name can be used. I
> used the macro to do typecasting but it's no
> longer necessary because I found a way to make
> the static names real PyObjects (probably the
> only place where something is actually defined
> as a PyObject!)

But the string is still more helpful in the code
than the symbol name.

Sorry, but none of this changes my position;
you'll hve to find another champion.
History
Date User Action Args
2007-08-23 15:14:40adminlinkissue593627 messages
2007-08-23 15:14:40admincreate