Related
I know that 3.0 is mostly UI improvements but I'm wondering if Google updated the JIT or made any other performance improvements with Gingerbread.
I know there was a CES presentation and we have a gingerbread ROM already... does anyone know if there were speed improvements made?
Oh I got 3.0 and gingerbread confused. I guess I'd be interested in hearing about both! lol
edit:
JVM speed. For Java developers, 2.3 adds a number of speedups, most notably a concurrent garbage collector. According to Google garbage collection pauses will be under 3ms, which is small enough not to be noticed in a 30fps or even 60fps game. New JIT optimizations make Dalvik code run even faster than before.
I remember when 2.2 was coming out we were able to use the JIT on our 2.1 ROMs... will we be able to backport 2.3's JIT?
FWIW, I compared CELBv3.9 to KGBv8 using Linpack @ min=max=748Mhz
(governor set to performance in both cases, but that shouldn't have any effect when min=max)
If you recall, that particular benchmark was/is pretty sensitive to whether JIT is operational.
The results? Over about 10 repeated trials each,
CELBv3.9: 4.75 - 5.05*
KGBv8: 4.68 - 5.28
There is an observable, but modest increase in the peak (maximum) value of the benchmark score in KGBv8 - roughly a 5% increase. But at the same time, note that the "scatter" in the benchmark actually worsened. I take that to mean that in real-world performance, it is unlikely that you will be able to notice a perceptible difference. Hard to know, really - synthetic benchmarks are pretty crappy predictors of the "pleasure of use" for an arbitrary application mix.
* Peak quadrant score was 429 for CELBv3.9 @ 748Mhz - quadrant currently fails in the 3D graphics tests in KGBv8
Thank you bftb0, very interesting results.
I think it's fair to attribute that scatter to the lack of optimization currently in place with that ROM. It is nice to see that it is capable of more though. Certainly when you use that ROM it's easy to see that the stable 2.2 ROMs are still going to give you better real world performance.
And idea as to whether we can backport the 2.3 JIT?
Hi, my name is Davis Woody. I'm a mechanical engineering student at UTC in Chattanooga, TN. I will be putting together this guide over the next few weeks. I am trying to be as scientific as possible with these scores so I will adhere to several rules for the tests. I would also love to test network strength, battery life, file transfer speed, and network speed but there are simply too many confounding variables. Can't wait to populate this thread.
My testing standards
1. I will allow each ROM to settle over the period of 12-24 hours before testing.
2. Identical applications will be installed on the different ROMs.
3. Identical phone settings (GPS, network, wifi, ect.) will be used during the tests
4. I will test 10 times at 1180mhz and 10 times at highest stable OC. I will note this maximum frequency in the data.
5. I will use a sample size of 10 tests to compute the sample average and standard deviation.
EDIT
If you would like for me to test a specific ROM and kernel combination, please feel free to ask. No request will be ignored.
It has been brought to my attention that Quadrant is not completely accurate for dual core. I am testing with CF Bench as well, the numbers seem to have a strong correlation.
ROM: VirusROM RC1 AOSP 1.13.651.7 2.3.3
Note: This ROM is so tight. It's about as close to CM as I've seen for the 3d. CF Bench is low for this ROM. My lowest quadrant was 3148. :O
Kernel: RCMix 2.6.35.10
Clock Freq.: 1836
CF Bench (mean score, std. dev)
Native: 7610.6, 123.80
Java: 2558.0, 66.50
Total: 4588.4, 82.80
Quadrant Standard (mean score, std. dev)
3650.3, 193.40
Underclock 1188mhz quad. score
2318, 62.64
ROM: Synergy ROM rev 318 w/ Sense 2.3.3
Note: Please note that I had disabled the EXT4 partitioning which can increase quad. scores. This is the fastest Sense ROM I've tested so far. Very stable w/ revision 318.
Kernel: RCMix 2.6.35.10
Clock Freq.: 1836
CF Bench (mean score, std. dev)
Native: 44202, 38.64
Java: 1791.6, 122.90
Total: 5555.4, 66.11
Quadrant Standard (mean score, std. dev)
3417.5, 245.55
Underclock 1188mhz quad. score
2215.2, 91.95
Underclock 1188mhz CF score
Native: 8569.0, 335.85
Java: 2150.3, 576.10
Total: 4660.5, 479.10
ROM: Showdown ROM 1 w/ Sense 2.3.3
Kernel: 2.6.35.14 Helicopter
Clock Freq.: 1836
CF Bench (mean score, std. dev)
Native: 11783, 650
Java: 2825.0, 675.72
Total: 6398.5, 592.3
Quadrant Standard (mean score, std. dev)
2920.3, 210.58
Underclock 1188mhz quad. score
2026.6, 128.68
ROM: Supra 1.5 AOSP 2.3.3
Note: Great ROM but it has its share of issues.
Kernel: SilverNeedles no lights 1.1.3
Clock Freq.: 1728
CF Bench (mean score, std. dev)
Native: 11341, 174.15
Java: 3270.2, 66.92
Total: 6498.2, 106.00
Quadrant Standard (mean score, std. dev)
2902.1, 205.72
Underclock 1188mhz quad. score
2125, 51.64
ROM: viperROM RC1.3 w/ Sense 2.3.3
Note: Great ROM for a daily driver.
Kernel: SilverNeedles no lights 1.1.3
Clock Freq.: 1728
CF Bench (mean score, std. dev)
Native: 11299.0, 117.80
Java: 3279.0, 40.0
Total: 6487.0, 65.71
Quadrant Standard (mean score, std. dev)
2798.2, 159.93
Underclock 1188mhz quad. score
2168.2, 84.35
ROM: Supra ROM 1.5 w/ Sense 2.3.3
Note: Great ROM for a daily driver.
Kernel: SilverNeedles no lights 1.1.3
Clock Freq.: 1728
CF Bench (mean score, std. dev)
Native: 11042, 239.4
Java: 3251, 152.2
Total: 6475, 125.4
Quadrant Standard (mean score, std. dev)
2773.33, 186.17
Underclock 1188mhz quad. score
2061.5,213.34
ROM: Douchless ROM w/ Sense 2.3.3
Note: Tether issues
Kernel: SilverNeedles 1.0
Clock Freq.: 1728
CF Bench (mean score, std. dev)
Native: 10787,192.2
Java: 1816,87.87
Total: 5404.8,120.86
Quadrant Standard (mean score, std. dev)
2647.8, 363.76
Underclock 1188mhz quad. score
2058.8,57.85
Underclock 1188mhz CF score
Native: 8748.4,118.7
Java: 1360.8,79.0
Total: 4321,95.2
ROM: SuperShooter3D(Bl00dy3dition)v.2 w/ Sense 2.3.3
Note:I'm not sure if this was a "clean" install. Got some FCs
Kernel: SilverNeedles no lights 1.1.3
Clock Freq.: 1728
Quadrant Standard (mean score, std. dev)
2239.8, 170.51
Underclock 1188mhz quad. score
1397.1, 269.10
chillfancy said:
Hi, my name is Davis Woody. I'm a mechanical engineering student at UTC in Chattanooga, TN. I will be putting together this guide over the next few weeks. I am trying to be as scientific as possible with these scores so I will adhere to several rules for the tests. I would also love to test network strength, battery life, file transfer speed, and network speed but there are simply too many confounding variables. Can't wait to populate this thread.
My testing standards
1. I will allow each ROM to settle over the period of 12-24 hours before testing.
2. Identical applications will be installed on the different ROMs.
3. Identical phone settings (GPS, network, wifi, ect.) will be used during the tests
4. Overclock speed will be at what I deem to be the highest stable level for each ROM. I will note this frequency in the data.
5. I will use a sample size of 10 tests to compute the sample average and standard deviation.
EDIT
If you would like for me to test a specific ROM and kernel combination, please feel free to ask. No request will be ignored.
It has been brought to my attention that Quadrant is not completely accurate for dual core. I am considering testing with CF bench as well.
Click to expand...
Click to collapse
you may as well leave off quadrant. its easily altered and not really accurate.
Seriously though, quardrant scores don't mean a much. The rom that claims to have the highest quads was not the fastest, but it was the most buggy (in my experience). And the rom I found to be the smoothest/fastest and lag-free had a quadscore 100 below stock lol.
chillfancy said:
...I am trying to be as scientific as possible with these scores so I will adhere to several rules for the tests. I would also love to test network strength, battery life, file transfer speed, and network speed but there are simply too many confounding variables...
My testing standards
1.
2.
3.
4. Overclock speed will be at what I deem to be the highest stable level for each ROM. I will note this frequency in the data.
Click to expand...
Click to collapse
Davis, If you're going to be scientific you've got to compare apples to apples, so ANY variables are unacceptable, including clock speed. To be completely objective, you need to compare all roms at 1.2Ghz (1188mhz) ... otherwise, any comparison is trash. The fact that a given kernel/rom combination can run at 2Ghz is nice, but it must be tested at 1.2Ghz for any comparison of battery life, data transfer rates, benchmarks, etc., to be meaningful.
Your goal is noble, but your method needs to be correct.
Good luck!
Success100 said:
you may as well leave off quadrant. its easily altered and not really accurate.
Click to expand...
Click to collapse
I don't think quadrant is completely useless. It does run full 2d and 3d to test the rendering performance.
oldjackbob said:
Davis, If you're going to be scientific you've got to compare apples to apples, so ANY variables are unacceptable, including clock speed. To be completely objective, you need to compare all roms at 1.2Ghz (1188mhz) ... otherwise, any comparison is trash. The fact that a given kernel/rom combination can run at 2Ghz is nice, but it must be tested at 1.2Ghz for any comparison of battery life, data transfer rates, benchmarks, etc., to be meaningful.
Your goal is noble, but your method needs to be correct.
Good luck!
Click to expand...
Click to collapse
I realized that testing at stock is important to really compare ROMs ,but with that said, a ROM that can run 1.8 stable is going to be a faster daily driver than one that crashes at 1.5. We'll see how the testing goes. And I'm not testing signal, battery life, or data rates.
chillfancy said:
I realized that testing at stock is important to really compare ROMs ,but with that said, a ROM that can run 1.8 stable is going to be a faster daily driver than one that crashes at 1.5. We'll see how the testing goes. And I'm not testing signal, battery life, or data rates.
Click to expand...
Click to collapse
Um, then I'm confused ... what exactly is it that you're testing? Are you just wanting to see which rom/kernel can survive the highest clock speed, regardless of battery life, or temperature (I guess?), or efficiency (however you want to define that)? If that's all you're doing, then why even bother with any "settling in" period at all? Heck, just keep cranking up the clock speed until the machine freezes or reboots, and report back to us, lol!
Carry on...
Quadrant is flawed to begin with. And you are testing with a flawed testing software for accurate results? Try this, run quadrant 5 times...you will see one of those scores will win, the others will vary widly. And this is on your phone!... Give me a break.
life64x said:
Quadrant is flawed to begin with. And you are testing with a flawed testing software for accurate results? Try this, run quadrant 5 times...you will see one of those scores will win, the others will vary widly. And this is on your phone!... Give me a break.
Click to expand...
Click to collapse
The sample size is 10. I'm running 2 different softwares. It's not just picking the highest outlier.
More power, but all your doing is spreading the myth of quadrant being the end all for performance. Not counting what apps are running, any tweaks each rom has..even stock and memory trash cleaning mechanisms, what natural speed of the phone is depending on the bus...yea it sure will be accurate....
So much venom in the forums... Geez.
So quadrants sucks. Oh well, as long as this guy isn't using the I/O tweak that shoots quadrants sky high, does several passes and than takes the average etc.
It sounds like he has a good foundation.
Except the whole overclocking thing. That kindof destroys your whole foundation and everything should be run at stock speed. Your taking all these steps to remove variants and then throwing a giant one in?
"Gentleman. We are going to study the effect of gravity on these rabbits. They will be weighted down at the base of there paws to keep them upright and from floating around.... Except this one. He will be stabbed, gutted and have the weight implanted into his abodmen. For funsies"
Just drop the overclocking part :-D
chillfancy said:
Hi, my name is Davis Woody. I'm a mechanical engineering student at UTC in Chattanooga, TN. I will be putting together this guide over the next few weeks. I am trying to be as scientific as possible with these scores so I will adhere to several rules for the tests. I would also love to test network strength, battery life, file transfer speed, and network speed but there are simply too many confounding variables. Can't wait to populate this thread.
My testing standards
1. I will allow each ROM to settle over the period of 12-24 hours before testing.
2. Identical applications will be installed on the different ROMs.
3. Identical phone settings (GPS, network, wifi, ect.) will be used during the tests
4. Overclock speed will be at what I deem to be the highest stable level for each ROM. I will note this frequency in the data.
5. I will use a sample size of 10 tests to compute the sample average and standard deviation.
Click to expand...
Click to collapse
Fantastic Idea and thanks for this! I'll be looking forward to seeing where they stand.... may I make a suggestion and start the testing after a reboot? Some roms performance varies and that'd make them all equal say .. hit the power button... wait a minute then start the ten tests.
Either way this will be a great reference for test jockeys
Although quadrant is not 100% reliable in determining how fast roms are but it will be interesting to see the results of each rom.
I'm just impressed that you are taking on such a tedious and time consuming test. Best of luck!
felacio said:
Except the whole overclocking thing. That kindof destroys your whole foundation and everything should be run at stock speed. Your taking all these steps to remove variants and then throwing a giant one in?
Click to expand...
Click to collapse
I like the overclocking test. Not including it would be like reading a car review and bashing them for testing a top speed higher than 75 MPH, since that's pretty much the highest speed limit you'll see anywhere.
Sure, you can state the 0-60 time and compare those, but who's gonna be hurt by knowing the top speed?
I want to see how well my rom will work when I crank that stuff up!
Assuming however, he does provide data for both the 1188 speed and the OC speed. Otherwise, he is just being silly. Lol.
BlaydeX15 said:
I like the overclocking test. Not including it would be like reading a car review and bashing them for testing a top speed higher than 75 MPH, since that's pretty much the highest speed limit you'll see anywhere.
Sure, you can state the 0-60 time and compare those, but who's gonna be hurt by knowing the top speed?
I want to see how well my rom will work when I crank that stuff up!
Assuming however, he does provide data for both the 1188 speed and the OC speed. Otherwise, he is just being silly. Lol.
Click to expand...
Click to collapse
Yeah... I don't agree with your analogy. But yeah, the OC should stay. But at the beginning it was forefront and he later decided to add the stock speed.
Your analogy fails because 75mph is 75mph. You can't go faster than 75 without going 76. And so on..
On the phone though. 1.2ghz can swing widely with how efficient the phone runs in that speed. It can be faster or slower depending on how the is is running. Look at Sense vs AOSP.. omg the difference! So the analogy that would work in that case is more "at 75mph. This car guzzles 20mpg. But this one does the same and at 30mpg" but at the end of that. Append ".. but the first car can go 180mph without an issue!"
Use linpack
Sent from my HTC EVO 3d
Root: revolutionary
Recovery: Twrp cwm 4
ROM: Synergy rls318 (I want aosp)
oldjackbob said:
...what exactly is it that you're testing?
Click to expand...
Click to collapse
Still waiting for an answer to this question.
Sorry, but I'm just not seeing the point to this whole effort.
mikedavis120 said:
Use linpack
Sent from my HTC EVO 3d
Root: revolutionary
Recovery: Twrp cwm 4
ROM: Synergy rls318 (I want aosp)
Click to expand...
Click to collapse
I'll consider it but CF Bench measures MFlops too so it might be a bit redundant.. It is taking me about an hour to collect and process the data on a single ROM already.
oldjackbob said:
Still waiting for an answer to this question.
Sorry, but I'm just not seeing the point to this whole effort.
Click to expand...
Click to collapse
The goal is to use testing standards, benchmarking software, and statistics to describe how the different ROMs score. I understand it isn't going to prove that once ROM is "better" than another but it will be very useful for others.
Cool I like it! Stock and OC is key! Also I think the max overclock is good too, if you find a rom that's stable at 2ghz(some people have done it) it'll help point others to those high speed roms. If you do come across one that's stable at 2ghz I would like to still see a 1.8ghz test.
For a battery test could you play a 5 or 10 min vid clip after a fresh reboot and a charge, then just record the percent dropped and voltage. Or just record the amount of batter drained before and after your bench marks. Using a app like battery indicator would be easy too.
ANTUTU BENCHMARKING :- The "OPEN" Discussion (11/12/12) 10125 BEST SCORE SO FAR
First things First
I HAVE THE EXTENDED BATTERY
Secondly
TO ME
Benchmarks DO gauge the ACTUAL Performance of MY phone (when pushed)
right your still reading
HELLO
BENCHMARKING
I've had my phone since day one of the uk release, and have flashed many many many roms, and kernels, and hboot's , experimenting with different oc programs, governors, frequencies and voltages, and ui in comparison to smoothness is greatly improved the higher the antutu score
REGARDLESS OF BATTERYLIFE.
that said.
the best concoction I cooked up, with the best ingredients from many experienced chefs (so far) is
Rom:- HTC Stock ICS LATEST
Kernel:-Yoda 10.1
Tweaks:- Pedja kernel tweak app v3.3.3/ Chainfire 3D/ Pimp My Rom
oc'd @ max and min 1.836 ghz
Uv @ 1312 mv
performance CPU Governor
I/0 Scheduler SIO @ 2048kb sd cache
No vsync
my score was]
10125
Please leave detailed Descriptions of
ROM
KERNEL
PATCHES
CPU GOVERNOR
I/O SCHEDULER
SD CLASS/SIZE
OV/UV CHANGES
THANKS IN ADVANCE
mOAr voltz
argument invalid, benchmark numbers does not equal performance. research how to trick benchmarking apps.
gav-collins1983 said:
first things first, I HAVE THE EXTENDED BATTERY. secondly, TO ME, benchmarks DO gauge the performance of MY phone, ......
right your still reading, hello,
benchmarking, I've had my phone since day one of the uk release, and have flashed many many many roms, and kernels, experimenting with different oc programs, governors, frequencies and voltages, and ui in comparison to smoothness is greatly improved the higher the antutu score, regardless of battery life.
that said.
the best concoction I cooked up, with the best ingredients from many experienced chefs (so far) is
leedroids rom v 5.3.0
leedroids kernel v4.1.0
system tuner pro 1.863 Max 192 min (added 0.25mv to 1.863 frequencie because it seemed to struggle)
and leedroids ondemand forced dual core patch
my score was 7004
rant over , lol
Click to expand...
Click to collapse
Jesus Christ is this what this site has came to?
bloodrain954 said:
argument invalid, benchmark numbers does not equal performance. research how to trick benchmarking apps.
Click to expand...
Click to collapse
it's not an argument, I clearly state, that this is to "ME" on "MY" phone,
also, I'm not trying to trick my benchmarking app, what I've seen over 28 weeks is a clear indication, to "ME" on "MY" phone , that ui is smoother and faster on higher benchmark scores, simple as that
Well duh, having an overclocked CPU results in higher benchmarks because the phone can complete things faster. This translates to a smoother UI.
The problem is that benchmarks are affected by so many things that might not reflect accurately the performance of the phone. And comparing different phones is useless because of skins and different hardware performing better in tests but worse in real life.
Faster CPU = higher benchmarks and smoother UI. That doesn't mean that higher benchmarks = smoother UI.
Sent from my HTC Evo 3D using XDA Premium App
SoraX64 said:
Well duh, having an overclocked CPU results in higher benchmarks because the phone can complete things faster. This translates to a smoother UI.
The problem is that benchmarks are affected by so many things that might not reflect accurately the performance of the phone. And comparing different phones is useless because of skins and different hardware performing better in tests but worse in real life.
Faster CPU = higher benchmarks and smoother UI. That doesn't mean that higher benchmarks = smoother UI.
Sent from my HTC Evo 3D using XDA Premium App
Click to expand...
Click to collapse
it does to me from what I've seen, I've made that white clear,
what's with all the hating on evo 3d , we never had this in the desire hd forums.
gav-collins1983 said:
it does to me from what I've seen, I've made that white clear,
what's with all the hating on evo 3d , we never had this in the desire hd forums.
Click to expand...
Click to collapse
Lololol your not in Kansas anymore
Sent from my SPH-D710 using XDA App
one time, at band camp...
sent from Evo
SoraX64 said:
Well duh, having an overclocked CPU results in higher benchmarks because the phone can complete things faster. This translates to a smoother UI.
The problem is that benchmarks are affected by so many things that might not reflect accurately the performance of the phone. And comparing different phones is useless because of skins and different hardware performing better in tests but worse in real life.
Faster CPU = higher benchmarks and smoother UI. That doesn't mean that higher benchmarks = smoother UI.
Sent from my HTC Evo 3D using XDA Premium App
Click to expand...
Click to collapse
No, not, duhhhhh, overclocking also causes instability in some cases, more so if incorrect/not optimized voltages per frequency and governor in kernel, and smooth ness is affected
gav-collins1983 said:
first things first, I HAVE THE EXTENDED BATTERY. secondly, TO ME, benchmarks DO gauge the performance of MY phone, ......
right your still reading, hello,
benchmarking, I've had my phone since day one of the uk release, and have flashed many many many roms, and kernels, experimenting with different oc programs, governors, frequencies and voltages, and ui in comparison to smoothness is greatly improved the higher the antutu score, regardless of battery life.
that said.
the best concoction I cooked up, with the best ingredients from many experienced chefs (so far) is
leedroids rom v 5.3.0
leedroids kernel v4.1.0
system tuner pro 1.863 Max 192 min (added 0.25mv to 1.863 frequencie because it seemed to struggle)
and leedroids ondemand forced dual core patch
my score was 7004
rant over , lol
Click to expand...
Click to collapse
People will hate me for this, and I waited a long time to post this on this thread, but I just have to do it.
Cool Story Bro.
tgruendler said:
People will hate me for this, and I waited a long time to post this on this thread, but I just have to do it.
Cool Story Bro.
Click to expand...
Click to collapse
:thumbup:
From the Beast : Galaxy Note
gav-collins1983 said:
first things first, I HAVE THE EXTENDED BATTERY. secondly, TO ME, benchmarks DO gauge the performance of MY phone, ......
right your still reading, hello,
benchmarking, I've had my phone since day one of the uk release, and have flashed many many many roms, and kernels, experimenting with different oc programs, governors, frequencies and voltages, and ui in comparison to smoothness is greatly improved the higher the antutu score, regardless of battery life.
that said.
the best concoction I cooked up, with the best ingredients from many experienced chefs (so far) is
leedroids rom v 5.3.0
leedroids kernel v4.1.0
system tuner pro 1.863 Max 192 min (added 0.25mv to 1.863 frequencie because it seemed to struggle)
and leedroids ondemand forced dual core patch
my score was 7004
rant over , lol
Click to expand...
Click to collapse
7000 score in Antutu @ 1.86 GHz? That seems low... I right around the same score at 1.65GHz
gav-collins1983 said:
first things first, I HAVE THE EXTENDED BATTERY. secondly, TO ME, benchmarks DO gauge the performance of MY phone, ......
right your still reading, hello,
benchmarking, I've had my phone since day one of the uk release, and have flashed many many many roms, and kernels, experimenting with different oc programs, governors, frequencies and voltages, and ui in comparison to smoothness is greatly improved the higher the antutu score, regardless of battery life.
that said.
the best concoction I cooked up, with the best ingredients from many experienced chefs (so far) is
leedroids rom v 5.3.0
leedroids kernel v4.1.0
system tuner pro 1.863 Max 192 min (added 0.25mv to 1.863 frequencie because it seemed to struggle)
and leedroids ondemand forced dual core patch
my score was 7004
rant over , lol
Click to expand...
Click to collapse
*Sips his Earl Grey* You like high numbers? You clearly did not like high numbers when you tipped me for my "bedroom" services!
gav-collins1983 said:
No, not, duhhhhh, overclocking also causes instability in some cases, more so if incorrect/not optimized voltages per frequency and governor in kernel, and smooth ness is affected
Click to expand...
Click to collapse
Anybody who knows anything about overclocking knows to make sure it's stable..
Seriously, if you think your high quadrants means your phone outperforms the leaked scores of a quad core Tegra 3 phone by almost double, then you're in denial.
Let me put this in words you can understand.
Faster clock speed = faster graphics and calculations.
Faster clock speed = higher benches.
Higher benches != better performance. They're just linked.
Sure, if you're pulling over 4000 in quadrant, your device is performing quite well. But that doesn't make your Evo 3D a super phone twice as good as the rest of ours.
There are so many factors involved that simply saying "my quads are high, and that indicates performance" is ignorant and naive. Once you can explain to me how your phone "performs" better than a quad core device, then maybe I'll spare your thoughts my time.
Sent from my HTC Evo 3D using XDA Premium App
I can't wait to see where this thread goes from here. Also, my phone is completely usable, fast, smooth, and has amazing battery life and I just scored an 1100 on Antutu. Benchmarks are worthless except to raise your eEsteem. See my thread about GeekBench from a few nights ago for proof.
Sent from my PG86100 using Tapatalk
Yes, as I stated in the other thread, quadrant is simply the equivalent of measuring mobile phone penis size and nothing more.
From the Beast : Galaxy Note
7000? Pics or get out.
Twitter: @knowledge561
Blog: knowledgexswag.tumblr.com
my score was OVER 9000!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
What! Over 9000! THERE'S NO WAY THAT CAN BE RIGHT!
What do benchmarks actually measure? I always make allkinds of tests to the phones i have just for fun and to compare to others i have understood that a bigger score is always better..?
Benchmark test with antutu shows for me
10372
I have a s3 16gb and using the latest stock ics..
Sent from my GT-I9300 using xda app-developers app
CPU tests i guess is based on really long loops and depends on time that loop take you get result. RAM tests I think write big file direct to memory and depend of time get you speed of RAM memory in MBps or GBps...
On Antutu I have about 14,9K-15K with Paranoid and Siayah kernel. On Quadrant i have about 5,7K
Sent from my GT-I9300 using xda app-developers app
e-peen.
Seriously, different benchmarks measure different types of system performance by subjecting different elements of the device to different stress and performance tests. CPU calculstions, frames per second, javascript performance - they're genuinely useful in some situations, such as for devs to test out different approaches and ideas to see if one works fundamentally better than the other, and if done properly it can be useful to compare raw performance of one device to another, but they've cottoned on in the wider community because some people like to benchmark their phones and post those benchmarks proudly.
It's all a bit ridiculous, especially if - indeed - they don't know what they're benchmarking, or they're using out of date and largely useless benchmarks like quadrsnt, or they're just doing it for the bragging rights. It's relatively easy to push your phone and have it score well in assorted benchmarking tools if you really want to, it's just unlikely to be genuinely useful in that state - for example, setting the CPU governor to 'performance' had the effect of boosting it up to the highest available clock speed, and of raping your battery life. These are mobile devixes, not gaming PCs, and are designed to operate accordingly.
Personally, I ignore people's benchmark posts, because if they're posting benchmarks they're either brsgging, complaining about something absurd - "Your kernel doesn't perform as well as someone else's when in this unrealistic benchmarking scenario! It may best optimised for daily use, but now I can't hold my precious benchmarking score above everyone else's heads!" or "This new software update sucks because I don't get as high as score in Wankermark Extreme! [twenty sad faces]."
Hope that helps.
Sent from my GT-I9300 using xda premium
onslaught86 said:
e-peen.
Seriously, different benchmarks measure different types of system performance by subjecting different elements of the device to different stress and performance tests. CPU calculstions, frames per second, javascript performance - they're genuinely useful in some situations, such as for devs to test out different approaches and ideas to see if one works fundamentally better than the other, and if done properly it can be useful to compare raw performance of one device to another, but they've cottoned on in the wider community because some people like to benchmark their phones and post those benchmarks proudly.
It's all a bit ridiculous, especially if - indeed - they don't know what they're benchmarking, or they're using out of date and largely useless benchmarks like quadrsnt, or they're just doing it for the bragging rights. It's relatively easy to push your phone and have it score well in assorted benchmarking tools if you really want to, it's just unlikely to be genuinely useful in that state - for example, setting the CPU governor to 'performance' had the effect of boosting it up to the highest available clock speed, and of raping your battery life. These are mobile devixes, not gaming PCs, and are designed to operate accordingly.
Personally, I ignore people's benchmark posts, because if they're posting benchmarks they're either brsgging, complaining about something absurd - "Your kernel doesn't perform as well as someone else's when in this unrealistic benchmarking scenario! It may best optimised for daily use, but now I can't hold my precious benchmarking score above everyone else's heads!" or "This new software update sucks because I don't get as high as score in Wankermark Extreme! [twenty sad faces]."
Hope that helps.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
200% agree but it wont stop the what is your quadrant score posts .
jje
it wont stop the what is your quadrant score posts .
Click to expand...
Click to collapse
Anyone good with Photoshop? Create a graph that reads 999'999'999'999'999'999 for your phone of choice and paste it under other people's claim.
It's neither more useful nor more useless than what they do
Benchmarks can be useful for yourself to check very basic performance before and after making changes (rom, kernel etc)
Sent via TCP/IP
gsw5700 said:
Benchmarks can be useful for yourself to check very basic performance before and after making changes (rom, kernel etc)
Sent via TCP/IP
Click to expand...
Click to collapse
Possible but run ten benchmarks one after the other and you get different results .
But as a method of a basic test to see if firmware has brought something extra to your phone yes .
Two areas of concern for users are always one use how the phone responds scrolls etc and that's subjective .Two is battery life and none of these benchmarks actually run a standard test that could be used to give a basic battery consumption figure over say a two hour period . But even that's not a good indicator of individuals battery usage .
jje
Hi guys,
I read many post that high benchmark score is just for fun or something like that. What matter is your daily usage, if it is smooth and responsive enough, then you can ignore benchmark result.
I am not completely agree with that. For me, benchmark score shows how efficient your ROM + kernel works.
If you get low score and not feel laggy, it means that you use your phone light enough, so even poor score doesn't matter for you.
For ex, when you open an excel file with a small data and simple calculation, it won't make much different whether you get lower/higher score in benchmark, it will open instantly. But when you open large excel file with complex calculation, then you will see the different.
Another example is when you run 3d benchmark with Antutu, with some ROM + kernel, it got around 25-30fps, another got 50-55fps. For gaming or app that use high def video a lot, surely, this will make a different.
Now, this is my experiences
1) On some ROM + kernel, I got Antutu's score around 22-23K, OC to 2496MHz
With this ROM + kernel, for daily usage, I don't feel any lag
2) On another ROM + kernel, I got Antutu's score around 32-35K, without OC
Since it has better score, I set it UC to 1.7Mhz and UV 100mAV and don't feel lag at all
So with a better score, I can UC and UV without effecting performance and the result is better battery life and if needed for heavy app, I can set it back to normal clock/volt to boost performance.
Regarding of this, choosing a ROM + kernel is not only based on performance, and I really-really appreciate ROM and kernel developer, they give ROM, kernel and times for free, hat's off for them, so
don't ask me with ROM + kernel that give best result
And then when you change just the kernel, what do you do?
Stock kernel, stock rom.. Antutu = 33K
Other kernel, stock rom... Antutu = 29K
Both at completely default settings. They both feel the same.
According to your theory, I should be able to UC and UV the stock kernel more then the other kernel, because it has a higher benchmark. But in practice, I have brought the other kernel down to 1.7 with no change in feel for actual usage. Bringing the stock kernel down to the same settings, there is more lag (as much as 3 seconds) opening some programs. Especially things that use the internet.
So the kernel that has the lower score can be underclocked more then the ne with the higher score. So the results are the opposite of what was predicted.
Things like changing TCP congestion to westwood have an effect on the responsiveness of some programs that isn't tested in the benchmark programs.
benchmarks really depend on the kernel...
I also experimented with different kernels.
I think benchmarks are for bragging right. some manufacturers have been caught fudging their benchmark scores.
So for me its not really that important.........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
souleman said:
Things like changing TCP congestion to westwood have an effect on the responsiveness of some programs that isn't tested in the benchmark programs.
Click to expand...
Click to collapse
Hi,
TCP congestion have nothing to do with "responsiveness of some programs" like you said, nothing like this (nor speed, smoothess) is improved when you change the TCP congestion...
It's only about network stuff... http://en.wikipedia.org/wiki/TCP_congestion-avoidance_algorithm.
So how the TCP congestion could affect the responsiveness of some programs???
For sure also nothing improved in benches like Antutu, Quadrant, etc... when you change the TCP congestion...
viking37 said:
Hi,
TCP congestion have nothing to do with "responsiveness of some programs" like you said, nothing like this (nor speed, smoothess) is improved when you change the TCP congestion... For sure also nothing improved in benches like Antutu, Quadrant, etc... when you change the TCP congestion...
It's only about network stuff... http://en.wikipedia.org/wiki/TCP_congestion-avoidance_algorithm.
So how the TCP congestion could affect the responsiveness of some programs???
Click to expand...
Click to collapse
How many programs on your phone use an internet connection? Like any messenger program, many games, etc etc.. How many sync to an online server? Like gmail, facebook, etc.
So changing the TCP congestion algorithm can help programs that use the Internet because they are able to access the online information better.
Ok.
You should have explained this in your first sentence, this is confusing
It's not what I (we) call "responsiveness" of programs, but maybe it's just me :angel:
I said that because I've even read from some users that TCP congestion improves speed and smoothness in general UI
Debate closed for me.
Speeds don't always = smoothness. Some roms are built for pure speed that take away from day to day memory pools to help push graphics.
Numbers are a good reference for overall phone speeds compared to others but take it with a grain of salt.
htcm7 said:
Hi guys,
I read many post that high benchmark score is just for fun or something like that. What matter is your daily usage, if it is smooth and responsive enough, then you can ignore benchmark result.
I am not completely agree with that. For me, benchmark score shows how efficient your ROM + kernel works.
If you get low score and not feel laggy, it means that you use your phone light enough, so even poor score doesn't matter for you.
For ex, when you open an excel file with a small data and simple calculation, it won't make much different whether you get lower/higher score in benchmark, it will open instantly. But when you open large excel file with complex calculation, then you will see the different.
Another example is when you run 3d benchmark with Antutu, with some ROM + kernel, it got around 25-30fps, another got 50-55fps. For gaming or app that use high def video a lot, surely, this will make a different.
Now, this is my experiences
1) On some ROM + kernel, I got Antutu's score around 22-23K, OC to 2496MHz
With this ROM + kernel, for daily usage, I don't feel any lag
2) On another ROM + kernel, I got Antutu's score around 32-35K, without OC
Since it has better score, I set it UC to 1.7Mhz and UV 100mAV and don't feel lag at all
So with a better score, I can UC and UV without effecting performance and the result is better battery life and if needed for heavy app, I can set it back to normal clock/volt to boost performance.
Regarding of this, choosing a ROM + kernel is not only based on performance, and I really-really appreciate ROM and kernel developer, they give ROM, kernel and times for free, hat's off for them, so
don't ask me with ROM + kernel that give best result
Click to expand...
Click to collapse
there is no any advantage .. this bench crap thing is just gimmick makes children happy when they have higher score than others..
Using your theory that means many high end android phones a year or two ago should have been much smoother than the iPhone which clearly was not the case
Sent from my LG-D802 using xda app-developers app
shadehh said:
Using your theory that means many high end android phones a year or two ago should have been much smoother than the iPhone which clearly was not the case
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
that is not theory ! that is my state !
u need to start read more 'bout benchmarks tho .. it is app (program) for stupid people naive and pathetic .. well smart people making money of stupid people
http://www.anandtech.com/show/7384/state-of-cheating-in-android-benchmarks
http://blog.gsmarena.com/almost-all-android-makers-cheat-on-benchmarks/
It's only my opinion (maybe read closely to get whole point)...
viking37 said:
Hi,
Instead of always say "benchmark means nothing", "benchmark are useless", "benchmark are not real life" (obviously), bla bla bla... Maybe the OP could know why his score are low or why there is too much difference?
Like for some other guys if almost everyone have, it's an example, about 35 000 in Antutu and one guy post because he have only 20 000, I think he could know why, what is wrong, etc..., right?
But no, each time there is always the same kind of "ready repplies" like above...
Benches can be useful if you know how to run them (and yes there is a manner to run a bench like CPU temp at the beginning, with data active or not, after reboot or not, etc...) and how you interprete them (the most important, at least for me), even Quadrant can be useful for a quick bench but it's just my opinion (ok Quadrant seems to have more variations than Antutu)... And i don't manipulate them (like with the FPS unlock, I mean the debug.egl... build.prop edit) after it's for fun too.
And if I tweak my device with VM, governor, i/o scheduler settings for example (and it is not manipulating, not for me, it's some real "tweaks" that you can judge too in real use, in general UI, user experience (improvement or not) and not only in benchs) I see in first in general UI and after I look in bench to see...
Yes don't get these benches as a scientist approach or the best accurate result or a result to garantie you a general user experience (bad or good), for example my main goal is about general UI (smoothess, speed, responsiveness) and after I play with benchs because it's always fun...
But the tendance, here on XDA, is to ban benches with always the same words and the same mind (because xx says benchs are useless, xy repeat the same thing without knowing anything or xx have a bad/low score so benchs are useless, etc, etc, etc...), it bothers me... (it's not directed to you in particular).
And in general the guys who post a result of bench post a screenshot of the overall score and nothing more... The most important is to know how you got this score (governor settings, rom, kernel, "tweaks", etc...) and the detailed score is also important.
A bench makes sense with explications and details on how and why you have this or that score.
I agree that a screenshot without information means nothing..., I'm the first to say that in different bench threads but people don't care and continue to post a screenshot only, it's absolutely ridiculous, but well...
It's like the battery stats or screen on time (and we have at least to thrads for that...), it's a kind of benchmark, but here people agree more with these (?) and same thing: 2 or 3 screenshots without any information (settings or usage) means nothing...
In preparation of car engine you run benchs (for the raw power) and you test also your car on street to see the comportement in general not only on a bench and also ther is some conditions to respect before run a bench like for a phone. It's the same thing for a device if you like tweak it, you tweak your device, you run bench to see the result, you use it in day to day use to see if there is an improvement or not (general UI, battery).
It's the same thing for a sportsman, the 100 m, marathon, etc... it's a kind of bench, you don't use it always in "real life" nor it suggests your real state but people don't shout against, right? But benches for phones, welcome to the drama... it's pathetic.
"It shows benchmark apps are no different than a random number generator...", false, I posted some Antutu scores in the benchmark thread (testing i/o scheduler) and I can say you I have accurate results (just keep in mind I was testing different i/o schedulers so the overall score varies a little) in 35 800-36100 range, nothing with 2/4 000 points difference. I can show you accurate results in Antutu with always the same settings like 36 000-36 100 range..., is it a random number generator? No, I don't think... You will always have a little variation, if it's a variation of 5 000 points then something is wrong (thermal throttling mostly, an app auto update, who knows?).
Things to retain: detail your scores, explain your setup and yes don't get the result as a condition on how your phone runs in day to day use, that being said I don't know where is there a problem with benchs on phone... and sometimes fun is nice...
Ok, end, to the OP it's probably due to thermal throttling, but you give very little information... so hard to say exactly but it seems you ran Antutu one after another?
You need to let your phone cool down between each run...
Sorry for this post but I had something to say... and yes I assume totally
Click to expand...
Click to collapse
I'll have one or two things to add but it will be even too long (even some kernel (Elite)devs uses benches to test some stuff, even some Elite devs who claims that benches are useless develops bench apps, etc...), and the general idea should be here I hope...
And stop insulting with "stupid people" please...
I have the LS 980 and just flashed OpTimuS DE 1.5 with Furnace kernel. I just ran Antutu for the first time and got 20396. The chart shows the LG G2 over 30k. So I ran a second time and got 9907. This isn't right.
The only benchmark you really need is you. Only you know what you want from your phone, how you use it and where and which part of it you need the most.
This benchmark pissing contest is more and more boring annoying with every passing day.