➜

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 pitrou
Recipients casevh, josh.r, mark.dickinson, pitrou, rhettinger, serhiy.storchaka, vstinner, yselivanov, zbyrne
Date 2016-02-03.17:52:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <56B23E64.8090907@free.fr>
In-reply-to <1454520061.84.0.704726214583.issue21955@psf.upfronthosting.co.za>
Content 
Le 03/02/2016 18:21, Yury Selivanov a écrit :
> 
> Yury Selivanov added the comment:
> 
>> Yury suggested running perf.py twice with the binaries swapped
> 
> Yeah, I had some experience with perf.py when its results were
> skewed
depending on what you test first.

Have you tried disabling turbo on your CPU? (or any kind of power
management that would change the CPU clock depending on the current
workload)
History
Date User Action Args
2016-02-03 17:52:40pitrousetrecipients: + pitrou, rhettinger, mark.dickinson, vstinner, casevh, serhiy.storchaka, yselivanov, josh.r, zbyrne
2016-02-03 17:52:40pitroulinkissue21955 messages
2016-02-03 17:52:40pitroucreate