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 zbyrne
Recipients casevh, josh.r, mark.dickinson, pitrou, rhettinger, serhiy.storchaka, vstinner, yselivanov, zbyrne
Date 2016-02-03.17:15:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1454519750.44.0.817883185358.issue21955@psf.upfronthosting.co.za>
In-reply-to
Content
> I don't understand what this table means (why 4 columns?). Can you explain what you did?

Yury suggested running perf.py twice with the binaries swapped
So "faster" and "slower" underneath "Baseline Reference" are runs where the unmodified python binary was the first argument to perf, and the "Modified Reference" is where the patched binary is the first argument.

ie. "perf.py -r -b all python patched_python" vs "perf.py -r -b all patched_python python"

bench_results.txt has the actual output in it, and the "slower in the right column" comment was referring to the contents of that file, not the table. Sorry for the confusion.
History
Date User Action Args
2016-02-03 17:15:50zbyrnesetrecipients: + zbyrne, rhettinger, mark.dickinson, pitrou, vstinner, casevh, serhiy.storchaka, yselivanov, josh.r
2016-02-03 17:15:50zbyrnesetmessageid: <1454519750.44.0.817883185358.issue21955@psf.upfronthosting.co.za>
2016-02-03 17:15:50zbyrnelinkissue21955 messages
2016-02-03 17:15:50zbyrnecreate