From: David Masover <ninja@...>
Date: 2009-03-14T07:53:07+09:00
Subject: Re: Ruby OpenGL Gears example that uses shiny and velvet GLSL shaders

Michael Brooks wrote:
> David Masover wrote:
>> Matthias Reitinger wrote:
>>> Michael Brooks wrote:
>>>  
>>>> On another topic, what kind of performance / fps are you getting?  My
>>>> past experience has been that Nvidia has better OpenGL drivers than 
>>>> ATI.
>>>>     
>>> reima@marvin:/tmp$ ruby gears_using_shaders.rb
>>> 14146 frames in  5.000 seconds = 2829.200 FPS
> >>
>>>> dave@SERENITY ~/tmp> 18 ruby -rubygems gears_using_shaders.rb
>> 22223 frames in  5.005 seconds = 4440.160 FPS
>> dave@SERENITY ~/tmp> 19 ruby gears_using_shaders.rb
>> 22217 frames in  5.000 seconds = 4443.400 FPS
>> dave@SERENITY ~/tmp> glxgears
>> 28008 frames in 5.0 seconds = 5601.509 FPS
> >
>
> Thanks for the feedback.
>
> Wow... I need a new computer.  You guys are killing my scores.

Not really... At one point, glxgears would refuse to report FPS unless 
you sent in a flag that was something like: 
--i-acknowledge-that-this-is-not-a-benchmark

Remember, running several thousands of frames per second is irrelevant, 
if your monitor is some 60 hz. What matters is if it can stay at 60 fps 
when rendering more interesting scenes than three spinning gears. 
Sometimes there's a correlation, sometimes not.

The only real use of glxgears as a benchmark is to test, definitively, 
whether your OpenGL is running in a hardware-accelerated mode, because 
the numbers are usually in the hundreds in software, versus thousands 
for hardware. But with CPUs getting faster, I'm not sure how long that 
will be the case -- Intel's new video card is supposed to be just a ton 
of x86 cores.

Now, if you want to compare FPS in Nexuiz, or Quake 4...