Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
LibreOffice 3.5.4 released
Posted May 30, 2012 21:37 UTC (Wed) by boog (subscriber, #30882)
Posted May 31, 2012 1:18 UTC (Thu) by bronson (subscriber, #4806)
Posted May 30, 2012 23:25 UTC (Wed) by mpr22 (subscriber, #60784)
Posted May 31, 2012 10:07 UTC (Thu) by SEMW (guest, #52697)
For small percentages, the two meanings of "X% performance gain" are more-or-less the same: "the task takes 5% less time than it used to" and "You can do 5% more tasks in the same time" correspond to more or less the same improvement (multiplying by 1-X is about the same as dividing by X+1 for X << 1). But as the percentage gets higher, the approximation gets worse: e.g. "the task takes 33% less time than it used to" corresponds to "You can do 50% more tasks in the same time".
Generally, we seem to have standardised on the first of those, and understand "X% performance difference" to mean something takes X% less time than it used to - hence all the comments on here.
So letting people use "100% performance gain" as meaning "You can do 100% more things in the same time" *isn't* harmless even if in that particular situation it's unambiguous, because it gets people used to using that second meaning of "X% performance difference" as well as the (more standard) first.
Posted May 30, 2012 23:34 UTC (Wed) by bojan (subscriber, #14302)
Posted May 31, 2012 4:57 UTC (Thu) by josh (subscriber, #17465)
Posted May 31, 2012 0:40 UTC (Thu) by jensend (guest, #1385)
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds