Originally posted by fenrus
View Post
Announcement
Collapse
No announcement yet.
Fenrus Linux: A Distro For Performance, Developers
Collapse
X

Originally posted by fenrus View PostI've been thinking about this, how to fix it, and I haven't figured it out yet. In some way, "50%" indicates "half as bad", and "+100%" is "twice as high". It also allows me to do math on the data points (the average of 25 fps and 75% fps is 50fps, and that math works also in 50% and +50%)
the primary objective for the graphs (for me at least) is to see if there's a regression, or an improvement, compared to a previous series of builds.
I do want to keep the graphs useful for that.
Comment

Originally posted by fenrus View PostI've been thinking about this, how to fix it, and I haven't figured it out yet. In some way, "50%" indicates "half as bad", and "+100%" is "twice as high". It also allows me to do math on the data points (the average of 25 fps and 75% fps is 50fps, and that math works also in 50% and +50%)
the primary objective for the graphs (for me at least) is to see if there's a regression, or an improvement, compared to a previous series of builds.
I do want to keep the graphs useful for that.
However, taking the average on your misleading graphs we would obtain (100%  50%)/2 = 25%, giving the false impression that your distro is a 25% faster on the average, when the truth is that both distros have the same average performance (i.e. your distro is 0% faster).
The problem here is that you are mixing a percentage (i.e. a relative value) with a baseline (i.e., a reference for an absolute value).
You do not need misleading graphs for seeing improvements or regressions. Your misleading graphs will be only giving a false appearance of performance in cases where there is none.Last edited by juanrga; 03272013, 11:25 AM.
Comment

Originally posted by fenrus View Postfwiw this linearity is useful, including for the graphing software (R with ggplot2) to calculate and draw the std deviation bars
Comment

Originally posted by juanrga View PostI appreciate your answer but if +100 points in a graph represent a 2/1 ratio (i.e., "twice") then 100 points would represent a 1/2 ratio (i.e., "one half"). If your distro is twice faster on test A, but the other distro is twice faster regarding test B then, on average, both distros have the same performance. This is the precisely the result obtained if you take the average of +100 and 100, which is zero. However, taking the average on your misleading graphs we obtain (100%  50%)/2 = 25% giving the false impression that your distro is a 25% faster on the average, when the truth is that both distros have the same average performance (i.e. your distro is 0% faster).
The problem here is that you are mixing a percentage (i.e. a relative value) with a baseline (i.e., a reference for an absolute value).
You do not need misleading graphs for seeing improvements or regressions. Your misleading graphs will be only giving a false appearance of performance in cases where is none.
Comment

Originally posted by Pallidus View Posthey fenrus will this remain your pet project or would you actually consider forming a small community and bring in more devs ?
(and writing docs isn't as interesting as integrating, say, gnome 3.8 as I was doing last night)
Comment

Originally posted by ryao View PostThis sounds sane to me. The sunspider benchmark does the same thing.
Comment

Originally posted by fenrus View PostNow I think you're confused. The average of "half as fast" and "twice as fast" is not "neutral" in any math that I can think of (before my morning coffee at least)
Consider this other example: three cities A, B, and C, whose distance between cities A and B is the same than between cities B and C. A red car travels at 40 km/h from city A to city B and at 20 km/h from city B to city C. Whereas a blue car travels at 20 km/h from city A to city B and at 40 km/h from city B to city C. What car is faster?
Using a methodology as yours, the red car is 100% faster than the blue car in the first span and 50% ("half as fast") in the second span. The average being 25% faster, which is not true.Last edited by juanrga; 03272013, 06:41 PM.
Comment
Comment