The graphics tests seem to be hitting vsync on the more modern devices

[GoogleCodeExporter]

Reported by George Yuan:

the graphics tests seem to be hitting vsync on the more modern devices, such as 
the new Droids and Galaxy phones. Basically, the frame rate of all your tests 
are artifically capped at 55-60fps, making it difficult to discern the 
performance differences between higher-end devices.

Two potential workarounds are to either increase the number of
iterations until you're running very low frame rates or modify the
benchmark to increase the amount of work drawn every frame until it
starts missing vsync, then use the “amount of work” as the benchmark
result.

Original issue reported on code.google.com by jserv.tw@gmail.com on 12 Nov 2010 at 2:48

• Merged into: Implement accurate graphics calculation methods (strict mode) #14

[GoogleCodeExporter]

Do you guys have a Galaxy phone to test 0xbench-2D on?
Modern 3D graphics benchmarks usually get very low framerate on present-gen 
architectures so that the tests can still be useful for future-gen 
architectures.
I think ideally, we should target 5-10fps for modern phones, e.g. Galaxy.

Original comment by georgela...@gmail.com on 17 Nov 2010 at 10:34

[GoogleCodeExporter]

Original comment by jserv.tw@gmail.com on 27 Jun 2011 at 8:53

• Changed state: Duplicate