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 alecsandru.patrascu
Recipients alecsandru.patrascu, brett.cannon, gregory.p.smith, lemburg, methane, pitrou, r.david.murray, scoder, skrah, steve.dower, zach.ware
Date 2016-03-04.07:18:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1457075911.33.0.0325673189975.issue25702@psf.upfronthosting.co.za>
In-reply-to
Content
From our experience, pybench only is not a representative benchmark. Instead, if you like to measure performance close to real workloads, you can run the Grand Unified Python Benchmark suite, that is more complete. 

Also, you need to take into consideration the hardware and software environment. For this, you can read the initial comment at this issue, section "Hardware and OS Configuration", to see the approach we have here at Intel.
History
Date User Action Args
2016-03-04 07:18:31alecsandru.patrascusetrecipients: + alecsandru.patrascu, lemburg, brett.cannon, gregory.p.smith, pitrou, scoder, r.david.murray, methane, skrah, zach.ware, steve.dower
2016-03-04 07:18:31alecsandru.patrascusetmessageid: <1457075911.33.0.0325673189975.issue25702@psf.upfronthosting.co.za>
2016-03-04 07:18:31alecsandru.patrasculinkissue25702 messages
2016-03-04 07:18:30alecsandru.patrascucreate