Message 224139 - Python tracker

➜

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	benjamin.peterson, dw, hynek, kmike, pitrou, scoder, serhiy.storchaka, skrah, stutzbach
Date	2014-07-27.15:48:35
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
> Even after totally isolating a CPU for e.g. django_v2 and with frequency scaling disabled, numbers still jump around for the same binary by as much as 3%. That's expected. If the difference doesn't go above 5-10%, then you IMO can pretty much consider your patch didn't have any impact on those benchmarks.

> Even after totally isolating a CPU for e.g. django_v2 and with frequency scaling disabled, numbers still jump around for the same binary by as much as 3%.

That's expected. If the difference doesn't go above 5-10%, then you IMO can pretty much consider your patch didn't have any impact on those benchmarks.

History
Date	User	Action	Args
2014-07-27 15:48:35	pitrou	set	recipients: + pitrou, scoder, benjamin.peterson, stutzbach, skrah, hynek, dw, serhiy.storchaka, kmike
2014-07-27 15:48:35	pitrou	set	messageid: <[email protected]>
2014-07-27 15:48:35	pitrou	link	issue22003 messages
2014-07-27 15:48:35	pitrou	create