Related
Just wondering is there any bench marks that can be run. I look at roms and everyone claims to be fast fastest faster but which one is the king of the roms. I dont have a clue
For Donut - http://forum.xda-developers.com/showthread.php?t=646587
For Eclair - http://forum.xda-developers.com/showthread.php?t=638835
Enjoy
what is a benchmark?
lay something on a bench and mark the bench
lay something not dissimilar on the bench and mark the bench
compare the marks..
plenty of benchmark apps on the market, none of them will tell you anything unless you record, repeat over and over and take averages for all the different ROMs
and even then it will only tell what is the best rom at doing stuff your phone wouldn't be doing day to day.
Just try the *all* different roms and stick with the one *you* like
Firerat said:
what is a benchmark?
lay something on a bench and mark the bench
lay something not dissimilar on the bench and mark the bench
compare the marks..
plenty of benchmark apps on the market, none of them will tell you anything unless you record, repeat over and over and take averages for all the different ROMs
and even then it will only tell what is the best rom at doing stuff your phone wouldn't be doing day to day.
Just try the *all* different roms and stick with the one *you* like
Click to expand...
Click to collapse
QFT!
There is a benchmark on the market called "Linpack" that measures MFLOPS. But... just because your phone may be able to calculate 4.5 MFLOPS doesn't mean that it will necessarily be the fastest for everyday operations (multitasking, gaming, etc.).
The best way is to keep a nandroid/bart/switchrom backup of your favorite and just go flash crazy until you find one that works the best for you.
Benchmark standardization would help clear up "A vs B" fight's I've seen in a many threads. I am still working on a battery life bench but here's my proposed testing standards and what I've been doing:
Tests are run from a fresh flashed phone. Software is run as it is (no change in settings). All tests are run three times with a computed average. The phone must be rebooted after each test to clear any data from the RAM. (BTW this takes fffooorrreeevvveeerrrr)
Software used: An3DBench, FPS2D, Linpack, NBench, NenaMark1 and Neocore.
Example:
ROM X Kernel X
An3DBench=3355
FPS2D=28 dev3.5
Linpack=33
NBench=2.69/4.049/0.92
NenaMark1=14.8
Neocore=25.9
Feedback and input would be greatly appreciated, then hopefully an agreed upon standard.
*Admin's, where would you like benckmark results posted? I'm sitting on 8 so far using the above methods.
Don't forget Quadrant.
Benchmarks are fun and all but in the end all that matters is how your phone runs and feels. If your happy, well that's all that matters.
Sent from my Evo CM6
+1 on quadrant
For battery life you could do two tests. One by letting the phone sit idle for like a hour or two and another by playing a movie or something for thats like 30mins or hour long. only thing that sucks is that will take forever!
I'd be willing to test a rom just pm me with witch one you want me to do.
funny part is these numbers mean NOTHING in the end it how YOUR phone run is what matters
drmacinyasha said:
Don't forget Quadrant.
Click to expand...
Click to collapse
As a few dev's have stated,and I've been able to duplicate, Quadrant numbers are easily manipulated at the kernel level. That's the reason I didn't include it in my tests.
Sporkman said:
funny part is these numbers mean NOTHING
Click to expand...
Click to collapse
Yes and no. For example An3DBench, NenaMark1 and Neocore scores mean nothing if FPS2D shows you have a high deviation. A high deviation affects gameplay, video playback, video recording and ui smoothness. I've benched a number of roms and kernels and the ones with the lowest FPS2D deviations stutter less on all areas. It's been brought up many times that the soft side needs help. As a tech going all the way back to 386's and IIe's, I've found that tests like these show where things are good and where things can be improved.
Just came back to the evo after leaving for Verizon and the evo I got seems to be slower than I remember. I was wondering on average how long it takes everyone else to load web pages and such mine loads fairly quickly but like i said not quite as fast as i remembered them. Also my YouTube app barely loads videos in hq they just sit and takes forever to load. Wondering if their might be something wrong with the phone that its not that fast or am I just remembering this phone being faster than it is. I love this phone i never wanted to get rid of it in the first place and if this is the way its supposed to be then so be it but i just want to make sure that everything is ok and in working order.
These all sound like quality of service issues, which could vary widely depending on signal strength, amount of bandwidth available, and of course whether or not you're on 3G, 4G or wifi.
It's hard to really troubleshoot something without any facts or details, maybe you can start with a speedtest for network speed and a CPU test for the actual phone speed. There are both in the market.
It said my cpu speed is 662.40Mhz and my speedtest is 581kbps download and 523kbps upload.
Also these test were done on 3g. 4g isn't very reliable in my area.
jhnnyblze2000 said:
It said my cpu speed is 662.40Mhz and my speedtest is 581kbps download and 523kbps upload.
Click to expand...
Click to collapse
CPU speed seems low as it is rated for 998MHZ stock. speed seems about right for 3g sadly
Not sure if I used the right program though so i could have givin the wrong number from the test what is the best program to do a cpu test? I used 2 different programs one was cpu benchmark that gave 998mhz and the first one i used was android cpu tester which gave the 662.40mhz. Should i take it back and try and get a new one or is this normal i'm not sure whats up or if its just me.
jhnnyblze2000 said:
Not sure if I used the right program though so i could have givin the wrong number from the test what is the best program to do a cpu test? I used 2 different programs one was cpu benchmark that gave 998mhz and the first one i used was android cpu tester which gave the 662.40mhz. Should i take it back and try and get a new one or is this normal i'm not sure whats up or if its just me.
Click to expand...
Click to collapse
Your CPU is fine. Just do a quadrant test, you should get ~1200-1300 stock.
Youtube/website not loading is because you are on a slow 3G connection.
Thanks for the help everyone i did the quadrant test 3 times first time i got 1191 but the second and third time i got 1296 so my phone looks like it is working the way it is supposed to. Just wanted to say thanks to everyone that helped me out on this.
so... why did you go.. and why you come back?
the 3g speeds seam a little slow...
it should be double that in download...
maybe.. it is just busier of late.
Dan330 said:
so... why did you go.. and why you come back?
the 3g speeds seam a little slow...
it should be double that in download...
maybe.. it is just busier of late.
Click to expand...
Click to collapse
4G + EVO = bad a$$
I thought the download speed seemed low too but I would think that has to do with the network and not my phone.
Hey everyone. Please Benchmark using Quadrant and Post your Score along with a screen shot or picture of your score.
Also please state if you tested your phone under default stock conditions, or if you rooted and tweaked the heck out of it to get the high score you got.
You can download Quadrant. Go To Android Market and search Quadrant.
MY Score : 2799
i can't upload the pic now
1.To prevent spam to the forums, ALL new users are not permitted to post outside links in their messages. After approximately eight posts, you will be able to post outside links. Thanks for understanding!
I am running CM 6.1 Stable and getting about 2300-2350 quadrant score (setCPU scaling between 245 and 1200). What are you running to get 2800?
Edit: Had weather bug running in the BG, now getting around 2500.
That's the highest quadrant score I've EVER seen from any first gen. Snapdragon device. What do you have it overclocked to? On my mt4g (second gen snapdragon with dedicated gpu) overclocked to 1600mhz on a deodexed, zip aligned rom, I just barely go above 2800 on quadrant.
I had an HD2 and a Nexus and never came remotely close to those numbers on any rom/kernel/clock speed combination. I've messed with and flashed many Evos, overclocked within reason, that also average literally half of that.
Since your post count is 2 and youve already opened a 'bragging rights' type thread, I'm going to have to call BS on this. Sorry, I just call it how I see it. Or hey, maybe you're just the chosen one and have a magic phone.
Sent from my HTC Glacier using XDA App
I am absolutely thrilled with a score of 2500. I have been using a G1 for the past year and a half and I decided it was finally time to upgrade. My G1 was only getting about 580 with CM 6.1 (and that was an amazing score). I was debating whether to get a MyTouch 4G, G2 or an HD2 with the Android off the SD card. I was able to pick up an HD2 for $200 off craigslist and boy I do not regret it. I don't know how this phone can run Android off the SD card faster than off the nand, but I am thrilled. By the way I am using a Class 10 4 GB SD Card, if that makes much of a difference.
Only this I wish it could do is play my 720p videos without the codec getting all blocky/laggy. But that is probably asking way too much.
Is 2500 on stock clock speed? There must be some serious speed enhancements here recently, last I used a dual booted HD2 it was only in the 1300 range, same with my nexus, and two Evos. My nexus will max around 1800 with the miui rom overclocked to 1100mhz or so..Is there something special with the HD2's hardware that I'm missing or is this the norm now?
Sent from my HTC Glacier using XDA App
I am using HD2ONE 0.3.4b based on CM 6.1 Stable (CM is awesome BTW). I am using setCPU to run the phone at 1190mhz clock, but it still gets great Benchmarks without. I have been using CM for about a year now on my G1. It is built for speed and memory improvements as these were necessities to keep my G1 alive and kicking up until now. I would assume anyone who can't break the 2000 point quadrant score might want to take a look at HD2ONE and CM.
PS.
Also, this is the T-Mobile HTC HD2, so perhaps the 1gb ram helps as well.
I still don't see the point in benchmarks. I used to have a build (it shall remain nameless) that got over 2400 in quadrant but the UI itself was slow as all hell. My current build (in sig) get's 1700 ish but is smooth as melted butter. I'd rather have a smooth OS than a cooked phone as well.
I'm not sure about your unnamed os but cyanogenmod is running smooth as butter
Sent from my HTC HD2 using XDA App
Ok and yet again here we go.
Your scores are so insane high because of what apears to be bug in the benchmarking of the SD card. Your device is NOT ultra wtf pownage fast. Its nothing to boast about. Its just a glitch. I had a build that did 3100 and still the build from darkstone is 100% faster and only pulling 1600 points.
Benchmarks are fun to measure on devices that run off NAND not SD so for the love of god STOP the benchmark topics.
shuntje said:
Ok and yet again here we go.
Your scores are so insane high because of what apears to be bug in the benchmarking of the SD card. Your device is NOT ultra wtf pownage fast. Its nothing to boast about. Its just a glitch. I had a build that did 3100 and still the build from darkstone is 100% faster and only pulling 1600 points.
Benchmarks are fun to measure on devices that run off NAND not SD so for the love of god STOP the benchmark topics.
Click to expand...
Click to collapse
I knew it had to be something to do with Android running off the SD card and not NAND, those numbers are just insane for the setups. Thank you for clearing that up sir.
shuntje said:
Ok and yet again here we go.
Your scores are so insane high because of what apears to be bug in the benchmarking of the SD card. Your device is NOT ultra wtf pownage fast. Its nothing to boast about. Its just a glitch. I had a build that did 3100 and still the build from darkstone is 100% faster and only pulling 1600 points.
Benchmarks are fun to measure on devices that run off NAND not SD so for the love of god STOP the benchmark topics.
Click to expand...
Click to collapse
Well it's not just a glitch. cedesmith's asynchronous data method actually does improve i/o by a huge amount. There are a few spots where the SuperRam build feels faster than the desire_hd2 and hd2one 3.4 but it's really not that big a difference. Plus the battery drain is not as good on the SuperRam.
This is one of the builds shuntje is talking about. Cedesmith's desire_hd2, running slightly overclocked at 1.19. No other tweaks.
I do not think that this result came from a gap in the program
my phone is so fast
now in benchmark >>> my socre is 2963 !!!!
add me in facebook and see the pic
facebook.com/home.php?#!/profile.php?id=100000362542194
Uploaded with ImageShack.us
buzz killington said:
Well it's not just a glitch. cedesmith's asynchronous data method actually does improve i/o by a huge amount. There are a few spots where the SuperRam build feels faster than the desire_hd2 and hd2one 3.4 but it's really not that big a difference. Plus the battery drain is not as good on the SuperRam.
This is one of the builds shuntje is talking about. Cedesmith's desire_hd2, running slightly overclocked at 1.19. No other tweaks.
Click to expand...
Click to collapse
how did u get that high io score ?
i can barley get 5k at 1.2ghz
ish i get higher score with lower oc just 1.07ghz
overall without 2d/3d 2560
cpu 5800
io 5900
1.11ghz
overall without 2d/3d 2600
cpu 6400 io 5700
civicvx94 said:
Is 2500 on stock clock speed? There must be some serious speed enhancements here recently, last I used a dual booted HD2 it was only in the 1300 range, same with my nexus, and two Evos. My nexus will max around 1800 with the miui rom overclocked to 1100mhz or so..Is there something special with the HD2's hardware that I'm missing or is this the norm now?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I don't know the details, but recently I've noticed a bunch of people here posting quadrant scores in the 2100-2400+ range.
I score about 2000 @1.19 Ghz, but my build is quite a bit older than the new ones.
There definitely seem to have been some optimizations done in the most recent builds, especially the one by darkstone which does something like load the entire android filesystem in memory or something.
I'll have to try a newer build.
poweroutlet said:
I don't know the details, but recently I've noticed a bunch of people here posting quadrant scores in the 2100-2400+ range.
I score about 2000 @1.19 Ghz, but my build is quite a bit older than the new ones.
There definitely seem to have been some optimizations done in the most recent builds, especially the one by darkstone which does something like load the entire android filesystem in memory or something.
I'll have to try a newer build.
Click to expand...
Click to collapse
Most all the big numbers come from the i/o improvements. You'll know if you see the build uses cedesmith's initrd. Using asynchronous read/write improves performance but also has a higher chance of corrupting the data file.
Just off the top of my head, these builds all are using it: cedesmith's desire_hd2, hd2one, jdms, darkstone's superram also uses it for his build.
i am using HD2ONE ROM , latest version.. my quadrant score is 2200+..
after flushing 10-15 ROMs its first time i got 2200+
i m running Radio 2.15.50.xx
yha, benchmarks are great braging rights.
ive run roms that bench silly high, but ive also run roms that bench " slow" but in real workd performance kick the crap out of the " fast" roms.
atleast some one did a benchmark from the payed version so it breaks it all down, and shows actual usefull info...
^^^^^^^^^^^^^^^^^^^
The reason its scoring so high is because of i/o. I believe that's the wrong metric to look at because i believe i/o is dependent on what memory card you have. If you pay attention to the other scores, all of these screenshots are right on par with the nexus one 2.2+. Still awesome, but don't brag that your benchmark is uber leet, as its probably the same or close to everyone else here regardless of build.
To test my theory, load the same build on another SD card, preferably one that has a lower class (lower read and write speeds) and then run the benchmark and post results.
I will also test a build with cedesmiths initrid explained earlier and post my results
Sent from my HTC HD2 using XDA App
Hi. Title says it all.
If anyone has a locked bootloader, stock ROM, stock launcher, (Basically new out the box), I'd love to see your AnTuTu benchmarks.
Also, I'd be interested in any other combination of unlocked/locked bootloader, STOCK ROM, and stock or 3rd party launcher. (If not stock rom, please post your BMs and details in the threads for your ROM )
THANKS! In advance (and when you post your screen). :good:
---
https://play.google.com/store/apps/details?id=com.antutu.ABenchMark
If you're new and want to help out, (because let's face it, who else has locked/stock/stock?) what you'll do is click that link above, choose to install, send to your Nexus 7. After a couple minutes or when your N7 notifies you that AnTuTu benchmark is installed, open the device, click the 2nd tab at top called "TEST" and then hit "Start Test".
This will take about 5 minutes. You'll get a benchmark screen but go ahead and give it a few more minutes, in fact on the first benchmark screen you see, (with a score at the top) if you tap the first divider labelled "Detailed scores", you'll see that more parts of your system are still being benchmarked. Make sure to pull down this DETAILED SCORES before taking the screen screen!
After that, and all benchmarking is done, hold power+vol down to take a screen shot. You can then post from your N7 to here or send it to yourself/etc to post the screenshot here.
Attached is an example (from my N7, which is unlocked/SGT7 ROM/modified stock launcher) of what it should look like.
Locked or unlocked has zero effect on performance/becnhmarks/battery etc. Effects nothing at all.
Sent from my Nexus 7 using Tapatalk 2
Thanks for your valuable input. albundy.
Thanks for the sarcastic reply after making a thread with such a silly idea to bench with a locked and unlocked bootloader.
It makes no difference. I am curious to how you can even ponder the idea that it could to be honest.
If you where so curious about it do it yourself. Waste your own time instead of trying get a noob to waste theirs. Anybody that isn't a complete newbie knows already it makes no difference and most would even know why.
albundy2010 said:
Thanks for the sarcastic reply after making a thread with such a silly idea to bench with a locked and unlocked bootloader.
It makes no difference. I am curious to how you can even ponder the idea that it could to be honest.
If you where so curious about it do it yourself. Waste your own time instead of trying get a noob to waste theirs. Anybody that isn't a complete newbie knows already it makes no difference and most would even know why.
Click to expand...
Click to collapse
I'm looking to gather benchmarks from a variety of configurations with stock ROM - that's the goal. The bootloader is quite obviously the least important part of this. I included it because there are quite a few people who may have unlocked and rooted and don't realize that it doesn't matter and to avoid filling the thread with meaningless posts that don't at all provide to the conversation like "Does it matter if I have unlocked my bootloader?". Basically, I was providing the detail that I would love to see benchmarking off *all* configurations with stock ROM.
antutu is mostly cpu speed dependant, with some infuence on 2d/3d scores if or if not you have force gpu acceleration enabled in developer options(device main settings). mostly, scores with similar cpu speeds will score the same(root or stock) if you bench with that cpu speed locked(for example 1200mhz high/1200mhz low). if you let the device scale(set cpu speed to the highest high and lowest low) then you wont know what cpu speed its actually benchmarking because the device scales and decides what cpu speed it wants. allowing it to scale can produce a huge variation in scores and is inaccurate in providing the true scores for a certain cpu speed, stock or root.