Last Updated: Oct 20,2010
Whats your mflops score on Linpack?
I was going to ask why and get into the various questions I have about people's fascination with Linpack - such as do any of you know what that means on your device, how many MLOPS are given over to integer DSP processors vs. other and all of that sort of boring reality.
But instead, I'd like to ask what phone and what rom your using.
Because it's not a stock EVO. Or you're doing a bit of task killing.
I get 6.9 - stock is around 5 or so.
I just got the same exact results as the Op
100% stock, 2 day old phone. That was with most apps closed but to be fair i also ran a test with a ton of apps open and pandora radio playing some foo fighters in the background and i still got 6.8
I have zero app killers on my phone btw.
I don't use a task killer at all. Phone has an UpTime of 135:12:25 (no idea if that matters) and fully stock, not rooted Evo and my results are identical to the op's
Stock (002 hw), 6.3 to 6.7.
Say, that is interesting.
My stock-like test matched Android Central's video comparing the EVO, Droid X and Nexus One - timecode 35 seconds - just over 5.
Either way - it means that Linpack is not that great a benchmark on Android.
The Andoid process management will righteously kill apps over time.
But hawkijustin's report of maintaining that speed "test with a ton of apps open and pandora radio playing some foo fighters in the background" is still interesting.
I admit, I thought you might have been trolling - apologies.
nope no trolling. I saw that video also and thought something was fishy with the evo he tested so i did my own tests and sure enough thats what i got. He has another video where he is testing the evo, droid (not droid x) N1, and some other att android phone and the evo he tested in that was getting 6.6+ each time.
Something was clearly wrong with the evo he used to test next to the droid x
I got 6.0 while tethering my computer via USB with several apps open. ATK uninstalled several days ago.
Edit: Make that 6.8 now.
Not necessarily - I've been sitting here popping open various apps - it will kinda go all over the place.
Linpack's MFLOP test is really meaningless - unless you're using it to show what's wrong with Android Central and the endless supply of creamy YouTubes mis-explaining tech!
It was designed for use in a different age, for a different class of machines, to judge application for a specific range of problems.
If you want to see more of what's wrong with that video, check out my link above, let me know what you think.
Interesting... I'm getting anywhere from 3.7 to 6.6 on my Evo, with the vast majority between 4 and 4.5.
I get between 6.5 and 6.8 running Damage Control 3.2 (no JIT), I still think these numbers will sky rocket when an official Froyo build comes about, although I really don't care since this is my phone not my gaming PC. If you want benchmarks ask my about my 3D Mark Vantage PC score, I could really care less if my phone can't run Need for Speed at 100fps.
I get 6.5-6.9. Doesn't matter if I have been using the phone all day or just turned it on.
I'm glad this came up. I don't understand why our EVO is so slow in this benchmark compared to the "top scores" or whatever they call it. Are people running ROMs tuned to increase this score?
usually get 6.93 to 6.97ish but just got this woot stock not rooted
6.8 to 6.9
Running DC's rom. And.... loving it.
Is something wrong with my phone? Im getting 20+, more in the 35s. Is higher worse? I have an htc evo. The scrolling is extremely lagging, and i've been trying to fix it to no avail..is my device defective?
Can somebody please explain what these numbers mean to those who are not tech savvy (like myself)?
In computing, FLOPS (or flops or flop/s) is an acronym meaning FLoating point OPerations per Second. The FLOPS is a measure of a computer's performance, especially in fields of scientific calculations that make heavy use of floating point calculations, similar to the older, simpler, instructions per second.
You can read the rest at Wikipedia if you want
No yours is perfectly fine. After the EVO was upgraded to Froyo (2.2) it now has a JIT compiler (just in time compiler) that makes the CPU and memory run much much more efficiently.
MFLOPS = Mega FLOPS = Mega Floating Point Operations Per Second.
In computer world - it basically measures how many calculations a CPU can do per second. Before Froyo, the EVO was only able to do around 7 million operations per second. Now, the EVO can handle 30+ MFLOPS. So that's why in the Google presentations about Froyo you will hear them say "it increases your performance about 4-5x" which this is basically demonstrating.
7 MFLOPS x 5 (times the performance) = 35 MFLOPS
Hope this helps
running this ROM and Kernal(version 1.3.1)... [ 9-29 ] Calkulin's EViO 2 ROM v1.3.1 [ 3.29.651.5 l OC l UV l Themeable ] - xda-developers
also wanted to include my quadrant score with this ROM and Kernal...
Linkpak 48, FPS 53, Benchmark 2300+
Separate names with a comma.