Linked by fsmag on Wed 13th May 2009 01:27 UTC
Permalink for comment 363301
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2005-10-31
Those who do not understand X are condemned to wrongly blame it, poorly, and to completely miss pinpointing the *real* culprits.
They need a more accurate and reflective set of benchmarks to that pinpoint exactly where the performance is seen and where that performance is lost. I am reminded of an article that once shed a bit of light on one of the most commonly used "X Benchmarks" .. glxgears
http://www.osnews.com/story/21133/Why_glxgears_Is_Slower_with_Kerne...