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 jacques
Recipients akitada, amaury.forgeotdarc, belopolsky, collinwinter, ezio.melotti, georg.brandl, giampaolo.rodola, gregory.p.smith, jacques, jaylogan, jhalcrow, jimjjewett, loewis, mark, moreati, mrabarnett, nneonneo, pitrou, r.david.murray, rsc, sjmachin, stiv, timehorse, vbr, zdwiel
Date 2010-12-31.09:23:52
SpamBayes Score 5.44266e-06
Marked as misclassified No
Message-id <>
Thanks for putting up the hg repo, makes it much easier to follow.

Getting back to the performance regression I reported in msg124904:

I've verified that if I take the hg commit 7abd9f9bb1 , and I back out the guards changes manually, while leaving the FAST_INIT changes in, the performance is back to normal on my full regression suite (i.e. the 30-40% penalty disappears).

I've repeated my tests a few times to make sure I'm not mistaken;  since the guard changes doesn't look like it should impact performance much, but it does.

I've attached the diff that restored the speed for me (as usual, using Python 2.6.5 on Linux x86_64)

BTW, now that we have the code on google code, can we log individual issues over there?  Might make it easier for those interested to follow certain issues than trying to comb through every individual detail in this super-issue-thread...?
Date User Action Args
2010-12-31 09:23:55jacquessetrecipients: + jacques, loewis, georg.brandl, collinwinter, gregory.p.smith, jimjjewett, sjmachin, amaury.forgeotdarc, belopolsky, pitrou, nneonneo, giampaolo.rodola, rsc, timehorse, mark, vbr, ezio.melotti, mrabarnett, jaylogan, akitada, moreati, r.david.murray, zdwiel, jhalcrow, stiv
2010-12-31 09:23:55jacquessetmessageid: <>
2010-12-31 09:23:53jacqueslinkissue2636 messages
2010-12-31 09:23:53jacquescreate