Thread: Evo 4g/Evo 3D
View Single Post
  #156 (permalink)  
Old 06-13-2011, 09:17 PM
BlackDynamite's Avatar
BlackDynamite
VIP Member
Offline
 
Join Date: Sep 2006
Posts: 1,839
Reputation: 1190
BlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on repBlackDynamite is halfway to VIP status based on rep
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Evo 4g/Evo 3D

Quote:
Originally Posted by gTen View Post
Linpack isn't running on any resolution...it only tests floating point...this is equivalent to Quadran'ts CPU score and GL benchmark's "CPU Performance: Float" benchmark...

aka its a benchmark that only measures 1 thing, the CPU and only in Float. And the score difference was 1%.

You can prefer it if you wish, but the benchmark fails to test the 2d and 3d GPU, CPU Int, I/O and memory.

BTW here is an official statement from the creator of linpack for android:



https://market.android.com/details?i...=search_result

Hence why I said Linpack only works for benching the same phone...so the author themselves said its not a good benchmark for cpu processors..now what?

There is no perfect benchmark yes, but Smartbench at the very least accounts for an overall performance of the device and is optimized to account for resolutions and dual cores.
He is not saying that THIS test doesn't work for testing CPU, he is saying that NO test works for testing CPU. He is clearly saying that since Android runs a Dalvik Java Virtual Machine, the best any test can do is test that virtual machine, rather than the actual machine. And that is also what I said- remember when I said that they weren't testing the dual core until the OS was designed that way?

The only way around this is with root access. Otherwise, what the linpack creator said is 100% correct- you are only testing the virtual machine and not the actual machine.
Reply With Quote