[Q] Linpack scores - Samsung Galaxy Nexus

If you check Engadgets review of the Galaxy Nexus, you will see it getting outgunned by the RAZR in Linpack.
Single thread: 42.85 vs 50.0 mflops
Multi thread: 69.37 vs 95.66 mflops
As I understand it they both contain SOCs from the same family with identical clocks. How do you explain the difference? Is there something in the kernel causing the CPU to underperform? Maybe its not running at the highest clock rating when running the benchmark?

1st. Who cares.
2nd. The OS is different and Linpack may not have been updated yet for ICS. This phone seems plenty fast.
Sent from my Galaxy Nexus using xda premium

I find these scores a waste of time. What really matters is how it responds to you in your daily use. That varies a lot from user to user and no scoring method will account for that...

Yes the phone is buttery smooth, I have no complaints in that department. However, this is a technical forum and it would be nice to figure out what exactly is going on here.

Guessing...
The software they used is not "aware" of the changes in ICS..;.

Related

[Q]Samsung Galaxy S "lag fix" for Inc?

Has anyone looked in to this to see if it is something that we could possibly port over/modify to work on our phones and benefit from?
http://forum.xda-developers.com/showthread.php?t=749495
I did a search and didn't see any topics started on this so I figured it was worth asking.
It increased the quadrant scores tremendously for the Galaxy S.
Non applicable.
Galaxy class phones have serious lag problems due to installation of apps on slow sd.
Sent from my ADR6300 using XDA App
If someone wants to compile a new kernel with the "fix" implemented, sure. You would need a class 6 sdcard to see any benefit from it though. The EVO guys are doing it and seeing numbers over 2000. There's no reason it wouldn't work. Though, you probably wouldnt notice any practical difference in the phone in regular use. I'm assuming the quadrant increase is due to the read write speeds being much higher using a card that fast, thus increasing the I/O score on quadrant.
What people don't seem to realize is that quadrant score is an average of the different tests, and not just a blanket score to use for comparisons...on the galaxy s it does fix the lag problem they have. Watch one do a quadrant test. The I/O test takes over a minute. A nice aide effect of the fix is that it inflates quadrant scores. The incredible is far from laggy, so you'd basically be doing it just to see a higher quadrant score.
You'd also have to figure out a way to use the Amon-RA recovery instead of clockwork, as only it can partition the sdcard in the correct way to implement this...
I'd actually love to see people try more things with the kernels, the ones we have are nice, but pretty basic. The EVO guys also have one that actively adjusts the cpu voltage based on speed and temperature, it's supposed to really increase the battery life. I guess that's probably due to the EVO not having the same supply shortages, and the fact they gave out a ton of them free to developers at the google conference, lol.

[Q] Benchmark questions!

First off I'm fairly aware of the fact that benchmarks are not accurate representations of the day to day real life usefulness of the handset.
That said, I used both linpack and quadrant standard edition for the first time tonight while testing another kernel with my current rom (which is cm7, ggingerbread-6).
At the conclusion of my testing it was very obvious that one kernel completely outclassed the other in a benchmarking situation, however something else became apparent that leads to this post.
If I follow and believe everyone else's benchmark scores, even those posted an hour earlier in the same kernel thread, then I might have the slowest Evo on planet earth.
I see other users of the same rom and kernal posting scores which are never below 1500 in quadrant, I saw one instance of 1300 but nonetheless, even overclocking to 1075 I can barely break 1100 and usually fall just below that. Sadly enough on the "slower" of the 2 kernals I was barely surpassing 900.
Now on the linpack side of things I don't have any comparative scores to judge against, but ill post what I received anyhow for information's sake. On the "faster" of the two kernels (the one that came prebuilt into the rom) I was getting between 33-34, on the new kernel I was testing I was getting between 19 and 22, these are all "mflops" of course, whatever that may be.
Someone give me some information or advice here! Do I just happen to have a slow evolution, or are others either exaggerating or using some trick/mod/tweak I'm royalty unaware of??
Thanks in advance!
some people brag, some people cheat, most have low scores, few have high, there isn't a very good baseline and the benchmark programs dont scale very well at all, I have run 1800 scores and I have run 600 scores, guess what. both roms were smooth and you wouldn't have been able to tell a difference, what does that mean? do we believe the benchmark programs? are they spitting a random number at us? who knows! dont believe them, be satisfied with how your evo is running and if it's not running very well then try a different kernel or rom, keep trying new ones until your satisfied, only then will some benchmark program output not mean a thing
Most of my Quadrant benchmarks with aftermarket ROMS+kernels have been in the 1100-1400 range, using VaelPak and various kernels to get most of the better scores there. The highest I've had was CM7RC1 with the SnapTurbo kernel, got an 1821. It was unusable, though.
I've come to the conclusion that the benchmarks aren't as important as battery life, especially with the Evo.
Biggest reason for the huge difference in numbers? Different versions of the app. The dev changed how it rates phones.
Sent from my PC36100 using XDA App
Thanks!
Explained. I knew they were totally not concurrent with the outward performance and usability of the device, and for what its worth while I've only ever flashed a total of 3 roms, this one is perfect for me and I seem to be one of the rare few with no problems whatsoever, everything works exactly as I would expect it to. So yes, l never feared my device was suddenly slower now that I knew the all knowing superultrabenchmark number.

Smartbench 2011

Didn't see a thread for this in here anymore so I thought I'd post. I know synthetic benchmarks don't mean a lot but I'm curious of what other people are scoring since mine seems to be lower than others tested.
My phone is a Telus SGH-T989D with a rooted stock rom with SetCPU running the system at 1.5 and have the V6 Tweak setup.
I find it interesting others have scored over 4000.
I was going to ask this same question. I tried smart bench on stock rom and the score was always between 2500 and 3400 when i see results of over 4000... I now have the Bombaridier v1.3 Rom and still get the same low results?
Is this normal score or could our phones have some cpu problems? Im thinking on going to T-Mobile and exchange the phone since it also has the camera pink spot problem and minor screen lines and spots on low brightness in dark colors...
finally had some time to sit down and enjoy my phone
Why are we getting our clock cleaned by so many other SGII models?
I don't know if this is a contributing factor, but they're using 2.3.3
We're using 2.3.5
To further this pattern, from what I understand, ICS is causing qudrant scores in the low 2000's and below on good phones..
The more advanced the OS version, the more it taxes the phone.. Just an observation.
I understand that it's fun to see your phone on top, but aren't these "benchmark" tests pretty irrelevant to performance and satisfaction? Is your phone laggy? Do you have any problems or is everything buttery smooth and running well? If it is then I wouldn't worry about arbitrary test results to be honest. You can run benchmarks over and over and get a different score every time. You can cheat on them. In the end just find a ROM/Kernel with the settings and features you like and enjoy it!
Yes that's true but every upgrade in OS uses more resources, so you're bound to see more lag on ICS than our current ROM
Sent from my SGH-T989 using xda premium
I guess not that many people use this one.

Good benchmarks

Hey guys I hear a lot of negative stuff about how smooth the GN isn't and how the hardware is not that good but I must say that after 6 months of SGS2 use with many awesome roms like Checkrom etc and overclocking to 1600Mhz running a lot of benchmark tests I have to say that my experience with the GN has been awesome. Its smooth, fast and pretty.
But I saved all my Antutu, Nenamark and Quadrant scores and i have done a series of scores with the GN trying different roms and kernels and I say that the results, even only clocked to 1350Mhz were on average above my old SGS2. We should consider how much more effort is required to use the resolution of the screen to produce 6800 scores on Antutu and 3000+ scores on Quadrant.
This phone is really the next logical step and I actually get it why Google went down this path.
robt772000 said:
Hey guys I hear a lot of negative stuff about how smooth the GN isn't and how the hardware is not that good but I must say that after 6 months of SGS2 use with many awesome roms like Checkrom etc and overclocking to 1600Mhz running a lot of benchmark tests I have to say that my experience with the GN has been awesome. Its smooth, fast and pretty.
But I saved all my Antutu, Nenamark and Quadrant scores and i have done a series of scores with the GN trying different roms and kernels and I say that the results, even only clocked to 1350Mhz were on average above my old SGS2. We should consider how much more effort is required to use the resolution of the screen to produce 6800 scores on Antutu and 3000+ scores on Quadrant.
This phone is really the next logical step and I actually get it why Google went down this path.
Click to expand...
Click to collapse
Nice to see a positive post for once.
Sweet as mate
I started a benchmark scores thread in general.
If you dont mind, can you post your ROM + Kernel and any OC/UV settings u applied.
Also, have u used CF-Bench and what was your score?
Cheers. Its big ie oc to 1350Mhz with Franco kernal.

Google edition roms lower benchmarks?

when I install a google edition or cyanogenmod rom or any rom thats not touchwiz I am getting lower scores just wondering why?
Lower's better. And all the TW junk in the background is taken out, leaving room for more processes, so of course it scores better.
Sent from my GT-I9505G using XDA Premium 4 mobile app
Tak23 said:
when I install a google edition or cyanogenmod rom or any rom thats not touchwiz I am getting lower scores just wondering why?
Click to expand...
Click to collapse
But does it feel faster? Because that's what really matters...
lordcheeto03 said:
But does it feel faster? Because that's what really matters...
Click to expand...
Click to collapse
This plus eleventy bagillion.
Benchmarks are totally arbitrary and meaningless.
TouchWiz ROMs scores great on benchmark tests because TW is specifically designed to perform well on such tests by putting the whole device into overdrive when the test is run. It doesn't mean that your day to day usage is better.
Tak23 said:
when I install a google edition or cyanogenmod rom or any rom thats not touchwiz I am getting lower scores just wondering why?
Click to expand...
Click to collapse
That's a very subjective statement. "Lower is better" really depends on the apo being used. Some, eg. Quadrant, a higher score is better. Linpack is the same way.
As said before, benchmark apps don't tell you the real performance of a device. Though they can give you a baseline or at least a general idea of different aspects. I wouldn't jump on the "benchmarks are useless" bandwagon as they do serve a purpose.
Sent from my SGH-M919 using xda app-developers app
KCRic said:
That's a very subjective statement. "Lower is better" really depends on the apo being used. Some, eg. Quadrant, a higher score is better. Linpack is the same way.
As said before, benchmark apps don't tell you the real performance of a device. Though they can give you a baseline or at least a general idea of different aspects. I wouldn't jump on the "benchmarks are useless" bandwagon as they do serve a purpose.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Well they are useless when ROMs are set up specifically to perform well on benchmark tests. That gives aboslutely no real world value.
The only time there is any validity to a banchmark comparison is when you are trying to compare 2 things that are set up almost exactly the same with only a single differing variable.
Like if you want to see if a phone is bad, you'd need to run a benchmark on the target phone and another on a different phone of the same model with the exact same settings. Or if you want to see in a mod if the cause of reduced performance, you would need to run a benchmark without the mod, then immediately after the mod, and repeat it several times to ensure you get repeatable results. Etc etc etc...
You can't just abandoned the scientific method and compare a benchmark of a TouchWiz rom with a benchmark of an AOSP rom with god only knows how many differences in the set up (kernel, clock speed, gpu settings, voltage, etc etc etc) and have it be a valid means of determining which is the better rom in any way. You can't even set it up properly so that all the settings match and the only difference is the ROM because there is so much incompatibility betweent the two that factors into it. Especially when the TouchWiz rom is set up with methods of inflating it's scores on benchmark tests and the AOSP ROM isn't.
I agree. Scientific method comes first in determining the performance of a ROM. Actually I would say real world and use experience is the best method. Given today's Hugh end phones, our for example, getting the most out of a benchmark or anything else serves little purpose. I can disable 2, even 3 core and still have a smooth experience with most daily a activities. Even underclocking the CPU & GPU still retains all the speed and usability.
I think most tech literate people use benchmarks just to see what the phone can do. Also, as a quick though fairly inaccurate method of determining if you're ROM and it's mods/scripts are efficient.
To answer the OP's question though - since AOSP is HW accelerated, has been for a while now, it should be "faster" and yield better benchmarks. Less running in the background. The most things are integrated as opposed to added on to the base ROM and code. That's a very generic and butchered explanation.
Sent from my SGH-M919 using xda app-developers app

Categories

Resources