4 ms·

315 FPS? I was told that frame rates over what you can actually see tells you very little about the actual performance. So implementation A at 315 FPS being 10

by geon 14y ago

315 FPS? I was told that frame rates over what you can actually see tells you very little about the actual performance. So implementation A at 315 FPS being 10% faster than B might very well be 50 % slower than B at 60 FPS. What is interesting is if the frame rate can keep a steady 30/60/120 FPS. Anything above that is just not indicative of actual performance.

jiggy2011 14y ago
Surely if they are both doing 60fps then by definition the performance will be the same? I guess the time spent doing the actual rendering vs waiting to do the next frame might be different, not sure if there is a reason that the characteristics would be different at 300FPS and 60FPS though since surely the only difference is how often the render code is called? Bare in mind that Valve is running this test on a much higher end PC than most consumers are likely to have. People will want to be able to run these games on their $500 laptops , so the difference between 270 and 315 FPS might translate into a difference between 50FPS and 60FPS which would be noticeable.
- lmm 14y ago
  If the code is "rendering" 300 FPS but only displaying 60, it could be doing anywhere from 1x to 5x as much work as if it were rendering at 60, depending on arbitrary driver internals. So it would be much more convincing if Valve had an example of "on this hardware, at these settings, it can sustain smooth 60fps under opengl and not under directx".
- geon 14y ago
  > the difference between 270 and 315 FPS might translate into a difference between 50FPS and 60FPS ...or it might not. Which is the problem. You can't just interpolate like that. Or can you? I have only heresay to go on.
kcbanner 14y ago
It completely is indicative of actual performance. You could turn on vsync in either of these applications and it would lock down to 60 FPS. The point is here, that with the same game implementation you have some more performance headroom on Linux. You could potential improve the engine in some way and use up that headroom, which would bring the performance into line but with some sort of graphical quality improvement on Linux (OpenGL).
- geon 14y ago
  > You could potential improve the engine in some way and use up that headroom That is a headroom of a factor of 5.25. If you use that headroom to implement better graphics, your performance characteristics will likely change completely. That's the point. A thousand vs. a million FPS when you draw a single unshaded triangle doesn't necessarily interpolate to predict the performance in a real scenario.
AshleysBrain 14y ago
Benchmarking is done with uncapped framerates to measure the relative performance of two systems. If you're a gamer, yes, you most likely won't see anything above 60 FPS, but the difference still matters if your hardware is 5x slower (54 FPS vs. 60 FPS)
naitbit 14y ago
I would agree that it may be better if they showed result for lowest FPS (instead of average) and on weaker system(were difference would matter far more). They probably tested on powerful developer workstation because it was the machine that they already program on.

by geon 14y ago

jiggy2011 14y ago

Surely if they are both doing 60fps then by definition the performance will be the same? I guess the time spent doing the actual rendering vs waiting to do the next frame might be different, not sure if there is a reason that the characteristics would be different at 300FPS and 60FPS though since surely the only difference is how often the render code is called? Bare in mind that Valve is running this test on a much higher end PC than most consumers are likely to have. People will want to be able to run these games on their $500 laptops , so the difference between 270 and 315 FPS might translate into a difference between 50FPS and 60FPS which would be noticeable.

lmm 14y ago
If the code is "rendering" 300 FPS but only displaying 60, it could be doing anywhere from 1x to 5x as much work as if it were rendering at 60, depending on arbitrary driver internals. So it would be much more convincing if Valve had an example of "on this hardware, at these settings, it can sustain smooth 60fps under opengl and not under directx".
geon 14y ago
> the difference between 270 and 315 FPS might translate into a difference between 50FPS and 60FPS ...or it might not. Which is the problem. You can't just interpolate like that. Or can you? I have only heresay to go on.

kcbanner 14y ago

It completely is indicative of actual performance. You could turn on vsync in either of these applications and it would lock down to 60 FPS. The point is here, that with the same game implementation you have some more performance headroom on Linux. You could potential improve the engine in some way and use up that headroom, which would bring the performance into line but with some sort of graphical quality improvement on Linux (OpenGL).

geon 14y ago
> You could potential improve the engine in some way and use up that headroom That is a headroom of a factor of 5.25. If you use that headroom to implement better graphics, your performance characteristics will likely change completely. That's the point. A thousand vs. a million FPS when you draw a single unshaded triangle doesn't necessarily interpolate to predict the performance in a real scenario.

AshleysBrain 14y ago

Benchmarking is done with uncapped framerates to measure the relative performance of two systems. If you're a gamer, yes, you most likely won't see anything above 60 FPS, but the difference still matters if your hardware is 5x slower (54 FPS vs. 60 FPS)

naitbit 14y ago

I would agree that it may be better if they showed result for lowest FPS (instead of average) and on weaker system(were difference would matter far more). They probably tested on powerful developer workstation because it was the machine that they already program on.