Quote:It represents performance but indirectly relative to time spent. For example if you used a speed percentance piledriver would have been about half the distance of haswell in the y axis at the right portion of the graph. Saying ghz is the most important aspect is therefore incorrect. Make a graph with a time scaling like this: 30:00 and then 15:00 and then 7:30 and then 3:15. Therefore each step will represent double speed to the previous step and the speed differences will be more clear.
I see what you mean. We wouldn't want people to think that Piledriver is almost as fast as Haswell. I didn't mean that GHz is more important than architecture, but it does make a difference in cases like this, and that's why I made the graph. Until I looked at the benchmark results, I wasn't sure whether Wolfdale@3.6GHz would be faster than Sandy Bridge@2.1GHz.
Quote:Or plot reciprocal time, which is speed, and therefore more useful.
That did cross my mind, but I didn't want to convert all the times to seconds.
Quote:Impossible to say with just that information. Too many other vairables to consider.
Things like the GPU, Dolphin version, OS, etc.. are not taken into account on the graph. If we assume that none of those things are causing a problem and they are using the latest version of Dolphin, I would put Joh Lie's CPU in a category like "Some games will run at playable speeds, probably not full speed."
Quote:Same problem as above. Plus I already did something like that awhile back. The thread got destickied because it wasn't considered specific enough
I remember your CPU hierarchy thread. It's really helpful. I think the graph format would help in the "Thoroughness vs. WTF am I reading?" department. You could include every architecture without creating a big wall of text.
Quote:Wait....why am I posting in the support subforum? I'm not supposed to be here. Damn you kinkin!
I miss reading your extremely thorough explanations of why people's computers were too slow for Dolphin.