[Speed] When CPython performance depends on dead code...

Victor Stinner victor.stinner at gmail.com
Wed Apr 27 11:07:34 EDT 2016


> For more benchmarks, see attached deadcode1.log and deadcode2.log:
> results of the CPython benchmark to compare deadcode1 VS reference,
> and deadcode2 VS reference run on my desktop PC (perf.py --fast & CPU
> isolation). Again, deadcode1 looks slower in most cases, whereas
> deadcode2 looks faster in most cases, whereas the difference is still
> dead code...

Sorry, I forgot to attach these two files. They are now attached to
this new email.

Victor
-------------- next part --------------
A non-text attachment was scrubbed...
Name: deadcode1.log
Type: application/binary
Size: 17183 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/speed/attachments/20160427/24e4cd2f/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: deadcode2.log
Type: application/binary
Size: 14486 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/speed/attachments/20160427/24e4cd2f/attachment-0003.bin>


More information about the Speed mailing list