Related
Look at this (from 1:44 on):
It's a quadrant benchmark run on a android port on the HD2. Graphics are really bad, but in the end it has approximately the same score as the benchmarking score of the Galaxy with the original firmware. I mean what is in a score? If I look at the beginning of the movie, the UI is very slow and not as responsive as the Galaxy
(BTW i got 55.7 FPS with the neocore benchmark on JM2)
This is not to say that I don't have deep respect for what the HD2-android development team is doing. Really amazing job. I just can't wait to get my HD2 back from repair.
appelflap said:
Look at this (from 1:44 on):
It's a quadrant benchmark run on a android port on the HD2. Graphics are really bad, but in the end it has approximately the same score as the benchmarking score of the Galaxy with the original firmware. I mean what is in a score? If I look at the beginning of the movie, the UI is very slow and not as responsive as the Galaxy
(BTW i got 55.7 FPS with the neocore benchmark on JM2)
This is not to say that I don't have deep respect for what the HD2-android development team is doing. Really amazing job. I just can't wait to get my HD2 back from repair.
Click to expand...
Click to collapse
Quadrant scores have been criticized for their non-descript breakdowns, at least on their free suite. Also, the fact that they chose the weighting of the scores, so should they chose 2D is equal to 3D weight, I don't know their formula (and for all I know, they give equal weighting to all or they give equal weighting to all test where the CPU has 12 tests and the 3D graphics has 4), but the fact that we, as users don't have access to their formula on their website is a bit unnerving.
Add to that the fact that many reviews and videos rely on it so heavily leaves users a bit misinformed. In reality, and thorough review should definitely run a custom test suite to give individual scores to:
CPU
Memory
I/O
2D graphics
3D graphics
That way users can compare what's important to them. The Galaxy S suffers from terrible I/O and the hacks that have given the fixes typically boost Galaxy scores to nearly double their rates, and it's majorly attributed to improving a bunk I/O score.
Totally agree. In addition, it would be really nice to know which benchmarked factors are responsible for which functions. For example it is really interesting to see how the hd2 performs before the user is running the tests. When the user is scrolling through the setting menu there is a very noticible lag. Given the fact that the total score is nearly the same as the scrore for the SGS, and thar the graphic score of the hd2 is bad in comparisson to the SGS, I would conclude that graphic performance is very important for the way the ui responds.
Sent from my GT-I9000 using XDA App
appelflap said:
Totally agree. In addition, it would be really nice to know which benchmarked factors are responsible for which functions. For example it is really interesting to see how the hd2 performs before the user is running the tests. When the user is scrolling through the setting menu there is a very noticible lag. Given the fact that the total score is nearly the same as the scrore for the SGS, and thar the graphic score of the hd2 is bad in comparisson to the SGS, I would conclude that graphic performance is very important for the way the ui responds.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
From what I can tell, the HD2 got a decent score 'cos it was running Froyo. When we get bumped up to an official froyo build with JIT fully optimized, We should be top of the pile.
don't forget, android isn't working 100% on the HD2.
I personally think it's pointless comparing to a not complete port.
woops dbl post
alovell83 said:
Quadrant scores have been criticized for their non-descript breakdowns, at least on their free suite. Also, the fact that they chose the weighting of the scores, so should they chose 2D is equal to 3D weight, I don't know their formula (and for all I know, they give equal weighting to all or they give equal weighting to all test where the CPU has 12 tests and the 3D graphics has 4), but the fact that we, as users don't have access to their formula on their website is a bit unnerving.
Add to that the fact that many reviews and videos rely on it so heavily leaves users a bit misinformed. In reality, and thorough review should definitely run a custom test suite to give individual scores to:
CPU
Memory
I/O
2D graphics
3D graphics
That way users can compare what's important to them. The Galaxy S suffers from terrible I/O and the hacks that have given the fixes typically boost Galaxy scores to nearly double their rates, and it's majorly attributed to improving a bunk I/O score.
Click to expand...
Click to collapse
Even then though, it's possible to write a benchmark which wins constantly for any phone.
In regards to "terrible I/O", that might even be due to a bug in the FAT32 drivers. Yes you can benchmark it, but it wont mean much. The best way is to actually TEST the applications you need, rather than select a phone based on benchmarks. However, you are possibly best off looking at the component specs, because they ignore software bugs.
scrizz said:
don't forget, android isn't working 100% on the HD2.
I personally think it's pointless comparing to a not complete port.
Click to expand...
Click to collapse
But the topic is about "what's in a score". Maybe one can generally say that is pointless to compare devices this way. I think that such benchmark scores are only (a bit) relevant at the two poles of the benchmark score spectrum. Everything in between can be neglected due to the uninformed way sub-scores are evaluated.
You got 55.7 FPS on Neocore as the sgs has vertical sync enabled, the refresh rate on the sgs'es screen is 56 fps and thus you can only go up to 56 fps as the v-sync is on. This proves that the sgs is indeed a much more powerful device that is actually being held back. If you can disable the v-sync then you can get a higher fps score
appelflap said:
But the topic is about "what's in a score". Maybe one can generally say that is pointless to compare devices this way. I think that such benchmark scores are only (a bit) relevant at the two poles of the benchmark score spectrum. Everything in between can be neglected due to the uninformed way sub-scores are evaluated.
Click to expand...
Click to collapse
I just read in a post that the Galaxy S gets a 0 on the 2D score:
"JIT isn't fully enabled in the current froyo versions, and quadrant, frankly, is bull**** (for exmple, 2d acceleration gets the same weight in the final result as 3D. Due to the fact that the SGS doesn't have a dedicated 2D accelerator, quadrant doesn't try to use the cpu- it just gives a round zero in that part)"
I can't confirm this, but that definitely seems like a terrible set-up, seeing as how I'm pretty sure I have games run in 2D, so to say that it can't do it just seems wrong regardless of if the SGS has a dedicated 2D accelerator or not (so if you aren't testing the way it performs in real-world, why are you testing?)
http://forum.xda-developers.com/showthread.php?t=737787&page=3
Qazz~ said:
You got 55.7 FPS on Neocore as the sgs has vertical sync enabled, the refresh rate on the sgs'es screen is 56 fps and thus you can only go up to 56 fps as the v-sync is on. This proves that the sgs is indeed a much more powerful device that is actually being held back. If you can disable the v-sync then you can get a higher fps score
Click to expand...
Click to collapse
It isn't really being held back - the screen can't display more than 56 fps as you say, and it wouldn't really be visible even if it could. Disabling v-sync isn't really that important, we need a benchmark that can actually use the advanced features in the SGS GPU (Neocore just pushes a fairly small amount of polygons with no real extras.) Using current 3D benchmarks to benchmark the SGS is like using quake 1 to benchmark the brand new ATI/nVidia cards.
The benchmark is what is at fault here, not the device
RyanZA said:
It isn't really being held back - the screen can't display more than 56 fps as you say, and it wouldn't really be visible even if it could. Disabling v-sync isn't really that important, we need a benchmark that can actually use the advanced features in the SGS GPU (Neocore just pushes a fairly small amount of polygons with no real extras.) Using current 3D benchmarks to benchmark the SGS is like using quake 1 to benchmark the brand new ATI/nVidia cards.
The benchmark is what is at fault here, not the device
Click to expand...
Click to collapse
I don't want to speak for the other poster, and I agree with your premise, however, it isn't actually solving the issue at hand. Better FPS wouldn't be noticed, however, it would give a better score and, more importantly, indicate it's potential. So, getting 56FPS isn't doing the phone any justice within the score, which is what reviews are using, giving it an artificially low score, and putting it more in line with units that can't compete on higher end games. So, when a site like anand pushes 150FPS on a game, I know that means that their rig is entirely too powerful for the game in question, but it still means something when you compare it to the lower end graphics card that only gets 90...then when they run Crisis you see these results play out more with differences that we can notice with the eye.
I think the HD2 gets that score because, as I can see in the video, the CPU tests run faster compared to my SGS, probably because of Froyo, and I know, from the time I had the Diamond and the HD2, that the internal memory and RAM are very fast. Sadly SGS has a slow internal memory, atleast when used by the phone`s software, when copying from PC is faster than my class 6 microSD. Luckily, we have mimocan`s fix. Hope this will be fixed in future FW`s.
NexusHD2 with-FRG83D V1.7 with hastarin r8.5.1 On my HD2 got 1920 in quadrant,31.5 on neocore, and 37 on linmark.
The lag might be because you are using launcher pro, I use launcher pro and sometimes it makes the the lock lag on my phone but it doesn't happen when I use the default lock also if you have alot of Widgets on your screen it will cause lag also
appelflap said:
Look at this (from 1:44 on):
It's a quadrant benchmark run on a android port on the HD2. Graphics are really bad, but in the end it has approximately the same score as the benchmarking score of the Galaxy with the original firmware. I mean what is in a score? If I look at the beginning of the movie, the UI is very slow and not as responsive as the Galaxy
(BTW i got 55.7 FPS with the neocore benchmark on JM2)
This is not to say that I don't have deep respect for what the HD2-android development team is doing. Really amazing job. I just can't wait to get my HD2 back from repair.
Click to expand...
Click to collapse
same galaxy s scores 6000+ in quadrant with custem roms
The HD 2 is a better fit for quadrent then the sgs as quadrent was made for the snapdragon processor which the hd2 has and the sgs does not. Comparing apples to orenges in an apple juice contest doesn't really prove much. Use real life feel. If you care about the scores a rom can be made to get you over 3000 quad score but is laggy as hell. Don't believe me? Look at my sig
interesting... I was using quadrant to see how a stock xxjvo and gingerreal compared. Surely that would indicate a real speed difference and not just be some kind of "hack" ?
zelendel said:
The HD 2 is a better fit for quadrent then the sgs as quadrent was made for the snapdragon processor which the hd2 has and the sgs does not.
Click to expand...
Click to collapse
That's right.
HD2 uses two android OS :
- Cyanogenmod, that is faster than our samsung os..
- Nexus one's port to HD2, greatly optimized by google...
It's really fast. I upgraded my father's HD2 last month, replacing windows in the NAND with CM7. It really makes a big change, the phone is like brand new ^^
http://forum.xda-developers.com/showthread.php?t=1012556
Quadrant is pretty flawed. And I say that being someone who had a phone (before modifications) that was mid-range in Quadrant (Galaxy S), and having a phone that's right top of the heap (Galaxy S II)
One of my coworkers has a tmobile vibrant with some lag fix according to him.. he did a quadrant benchmark right in front of me and it was showing 2500 plus everytime.. Im very curious as to what is making his phone so fast. And can it be dont to ours. Hes not running a custom rom or overclocking. Im only getting 1030 with mine clocked at 1.2ghz. Any Ideas? I couldnt get into too much details with him yesterday and I dont know whens the next time ill see him..
If you were to look at a test break down you would see generally all the scores are identical or the epic a little ahead except in the read/write area. The scores from their read/write are just inflating their overall score. It's a issue with quadrant and how it handles its overall score. Basically it just makes the system easy to abuse/cheat. So I wouldn't worry much about the difference in your score and his.
Sent from my Samsung Epic
The reason other Galaxy S phones score high in quadrant is because of the lag fix they use. The lag fix mounts a different file system on the phone with DRAMATICALLY increases read-write times. That portion of the quadrant benchmark gets inflated beyond reason. Using this game technique, Cyanogen was able to score more than 3000 on a snapdragon phone.
All of the Galaxy S phones have the same processor. Also, quadrant is a terrible benchmark. It's the most over-quoted and abused benchmark for android phones
Ahh ok.. thats good to know.. so what would be a better benchmark to use? Linpack?
jok3sta said:
Ahh ok.. thats good to know.. so what would be a better benchmark to use? Linpack?
Click to expand...
Click to collapse
Linpack is good for measuring raw CPU processing power... but only on devices running the same version of android. Phones with 2.2 will score insanely high due to the JIT compiler. For example, a snapdragon phone with Froyo can score ~40 Mflops. A snapdragon phone with eclair scores around 7 Mflops. Does Froyo make the phone run 5-6X faster? Hell no. In some cases, the difference is almost unnoticeable to the human eye.
Here is a rundown of what I believe to be the pros and cons of various benchmarks:
Linpack
Pros:
- Good for measuring CPU processing power on the same version of Android
- Great tool for measuring the performance gain from overclocking
Cons
- Scores are boosted unreasonably by Froyo's JIT compiler on snapdragon phones
Quadrant
Pros:
- Great tool for measuring the performance gain from overclocking
- Decent tool for measuring 3D graphics performance (just pay attention to FPS, not the end result)
- Decent tool for measuring 2D graphics performance (again, look at FPS)
- The paid version ("Quadrant Pro" I believe) shows which parts of the benchmark contributed to the score. Easier to spot the inflated CPU or I/O inflation
Cons:
- I/O portion isn't valued as much as others, but can boost scores beyond reason via exploits, hacks, fixes, etc.
- CPU portion is inflated on phones running 2.2. A Nexus One is not faster than any Galaxy S, Droid X, Droid 2, etc.
Neocore
Pros:
- Good tool for measuring graphics processing power
Cons:
- Graphics are not intense enough to push the power of very fast GPU's. Some phones will hit their FPS limit
- Only measures graphics processing power.
Nenamark1
Pros:
- Great tool for measuring graphics processing power
- Effects are advanced enough to show the performance of faster GPUs in relation to phones with lesser GPUs.
Cons:
- Only measures graphics processing power.
Sweet thanks for all the info man..
Agreed, this is great info thanks. I think the quadrant score is the most quoted becuase it provides a very easy to read graph built in with it for instant comparing/gratification. I guess I am gonna start going by linpack and nenamark1.
hydralisk said:
Linpack is good for measuring raw CPU processing power... but only on devices running the same version of android. Phones with 2.2 will score insanely high due to the JIT compiler. For example, a snapdragon phone with Froyo can score ~40 Mflops. A snapdragon phone with eclair scores around 7 Mflops. Does Froyo make the phone run 5-6X faster? Hell no. In some cases, the difference is almost unnoticeable to the human eye.
Click to expand...
Click to collapse
Linpack is ok for when your using same CPU comparison, different CPU's can cause issues...The reason why snapdragon gets scores of 5-6x is for some reason the snapdragon utilizes the VFP rather then using raw processing power..aka snapdragon cheats on the Linpack.
In reality our I/O scores should be a lot higher then it is as even in the Epic some of samsung's crappy file system still exists. But not as high as the lagfixed Vibrant of course.
Quadrant Pro is probably best indicator out of them all(The non-pro version is pretty much useless unless your comparing the same phone)...the con of having 2.2 show is higher is expected as it is a measure of efficiency of JIT in comparison to the current. The OS always played a role in Benchmarks so it is expected.
it can be faked by using a different partition to test on. IIRC the data partition making the speeds much faster than they should be so be careful when accepting those high scores
rjmjr69 said:
it can be faked by using a different partition to test on. IIRC the data partition making the speeds much faster than they should be so be careful when accepting those high scores
Click to expand...
Click to collapse
It is not exactly faking it..as you are increasing performance..thing is you cannot see at what it performs well at unless you see the individual scores from the Pro version....
both running 2.2 (epic on dk28)
epic gets 991-1000 and the evo just scored 1241... wtf?!
the evo isn't EXT4 is it?
the epic is currently RFS... I'm having problems going to EXT4
The Quadrant was made specifically for the Snapdragon process; which the Evo uses if i'm not mistaken.
Besides; they don't prove real world performance. I've gotten my hands on numerous evo's and all seemed to be 'laggy' they arn't nearly as responsive as my Epic.
Quadrant scores do not accurately represent Snapdragon vs the Galaxy S Hummingbird (or any other Cortex-A8 like those in Verizon's Droid lineup). Certain functions such as the Virtual Floating Point extension in Snapdragon allow for artificially inflated Linpack scores which do not represent real-world performance. Additionally, the RFS file system that Samsung uses on the Galaxy S phones is not well-understood by Quadrant, resulting in drastically lower scores.
For example, when we switch to EXT4 from RFS, our FroYo Quadrant scores can jump from 1100 to the 1600 range (which kicks the pants off that EVO). The actual performance increase however is hardly perceptible.
In short, Quadrant sucks, and Linpack is susceptible as well. For ****s and giggles, a little while back I made a minor modification to my Epic and produced a Quadrant score of 2597, which is currently listed as the 10th highest score on SmartphoneBenchmarks.com, and is the highest stock clock Quadrant score recorded. I accomplished this score utilizing a simple hack devised by a few developers here on XDA that fools the Quadrant application by utilizing a ramdrive for the I/O test. I posted about it on their forums and was advised by an administrator that they are aware of the problems with Quadrant and are releasing their own benchmark tool.
Android runs on top of a virtual machine so really what you're testing is virtual machine performance, and currently that virtual machine is tweaked for Snapdragon. With the Nexus S now a Google flagship phone, we'll likely see the VM better optimized for Hummingbird in the near future, and in fact, Gingerbread had a few more JIT enhancements as well.
Hummingbird is a slightly better performing chip MHz for MHz than the first-generation Snapdragons, if by a small amount. However it is significantly more power-efficient. Second-gen Snapdragons do draw even in terms of efficiency and performance, but both are going to be blown away by the Cortex-A9 Tegra phones we'll be seeing this spring.
EDIT - So I just noticed that SmartphoneBenchmarks.com has released their own benchmark tool recently, Smartbench 2010. I just ran it on my phone and scored 1178 on the Productivity Index (CPU) and 2610 on the Games Index (GPU). The highest-scoring competitor, the HTC G2, scores 1045 and 1396 respectfully. DRockstar on IRC ran the benchmark on his Epic that has RFS, and scored 1133 and 2521. So, this benchmark tool actually performs fine on RFS. Amazing! Grab it off the Android Market!
Electrofreak said:
Quadrant scores do not accurately represent Snapdragon vs the Galaxy S Hummingbird (or any other Cortex-A8 like those in Verizon's Droid lineup). Certain functions such as the Virtual Floating Point extension in Snapdragon allow for artificially inflated Linpack scores which do not represent real-world performance. Additionally, the RFS file system that Samsung uses on the Galaxy S phones is not well-understood by Quadrant, resulting in drastically lower scores.
For example, when we switch to EXT4 from RFS, our FroYo Quadrant scores can jump from 1100 to the 1600 range (which kicks the pants off that EVO). The actual performance increase however is hardly perceptible.
In short, Quadrant sucks, and Linpack is susceptible as well. For ****s and giggles, a little while back I made a minor modification to my Epic and produced a Quadrant score of 2597, which is currently listed as the 10th highest score on SmartphoneBenchmarks.com, and is the highest stock clock Quadrant score recorded. I accomplished this score utilizing a simple hack devised by a few developers here on XDA that fools the Quadrant application by utilizing a ramdrive for the I/O test. I posted about it on their forums and was advised by an administrator that they are aware of the problems with Quadrant and are releasing their own benchmark tool.
Android runs on top of a virtual machine so really what you're testing is virtual machine performance, and currently that virtual machine is tweaked for Snapdragon. With the Nexus S now a Google flagship phone, we'll likely see the VM better optimized for Hummingbird in the near future, and in fact, Gingerbread had a few more JIT enhancements as well.
Hummingbird is a slightly better performing chip MHz for MHz than the first-generation Snapdragons, if by a small amount. However it is significantly more power-efficient. Second-gen Snapdragons do draw even in terms of efficiency and performance, but both are going to be blown away by the Cortex-A9 Tegra phones we'll be seeing this spring.
EDIT - So I just noticed that SmartphoneBenchmarks.com has released their own benchmark tool recently, Smartbench 2010. I just ran it on my phone and scored 1178 on the Productivity Index (CPU) and 2610 on the Games Index (GPU). The highest-scoring competitor, the HTC G2, scores 1045 and 1396 respectfully. DRockstar on IRC ran the benchmark on his Epic that has RFS, and scored 1133 and 2521. So, this benchmark tool actually performs fine on RFS. Amazing! Grab it off the Android Market!
Click to expand...
Click to collapse
Electrofreak,
I just wanted to thank you (I pushed the button, too!) for this post. I'm trying to decide between three phones for my Sprint upgrade next month. My three candidates are the Epic, Evo, & new Evo Shift.
I was not aware of everything you stated, so it helped me look at the Epic in a different light.
Again, thanks.
tps70 said:
Electrofreak,
I just wanted to thank you (I pushed the button, too!) for this post. I'm trying to decide between three phones for my Sprint upgrade next month. My three candidates are the Epic, Evo, & new Evo Shift.
I was not aware of everything you stated, so it helped me look at the Epic in a different light.
Again, thanks.
Click to expand...
Click to collapse
No probs, and if you're interested in still more info, you're welcome to read an article I wrote comparing the hardware in multiple smartphones back in April (though the focus was on the EVO 4G and the Samsung Galaxy S I9000). The article is starting to get a little outdated, (neither the EVO nor the Galaxy S line had been released at that point yet) and it also doesn't cover some other details I've unearthed since then (my blog in my signature is where you'll find that) but most of it is still relevant.
http://alienbabeltech.com/main/?p=17125
Edit - I think I have an addiction to parenthesis (which I'm ashamed to admit)
Electrofreak said:
Quadrant scores do not accurately represent Snapdragon vs the Galaxy S Hummingbird (or any other Cortex-A8 like those in Verizon's Droid lineup). Certain functions such as the Virtual Floating Point extension in Snapdragon allow for artificially inflated Linpack scores which do not represent real-world performance. Additionally, the RFS file system that Samsung uses on the Galaxy S phones is not well-understood by Quadrant, resulting in drastically lower scores.
For example, when we switch to EXT4 from RFS, our FroYo Quadrant scores can jump from 1100 to the 1600 range (which kicks the pants off that EVO). The actual performance increase however is hardly perceptible.
In short, Quadrant sucks, and Linpack is susceptible as well. For ****s and giggles, a little while back I made a minor modification to my Epic and produced a Quadrant score of 2597, which is currently listed as the 10th highest score on SmartphoneBenchmarks.com, and is the highest stock clock Quadrant score recorded. I accomplished this score utilizing a simple hack devised by a few developers here on XDA that fools the Quadrant application by utilizing a ramdrive for the I/O test. I posted about it on their forums and was advised by an administrator that they are aware of the problems with Quadrant and are releasing their own benchmark tool.
Android runs on top of a virtual machine so really what you're testing is virtual machine performance, and currently that virtual machine is tweaked for Snapdragon. With the Nexus S now a Google flagship phone, we'll likely see the VM better optimized for Hummingbird in the near future, and in fact, Gingerbread had a few more JIT enhancements as well.
Hummingbird is a slightly better performing chip MHz for MHz than the first-generation Snapdragons, if by a small amount. However it is significantly more power-efficient. Second-gen Snapdragons do draw even in terms of efficiency and performance, but both are going to be blown away by the Cortex-A9 Tegra phones we'll be seeing this spring.
EDIT - So I just noticed that SmartphoneBenchmarks.com has released their own benchmark tool recently, Smartbench 2010. I just ran it on my phone and scored 1178 on the Productivity Index (CPU) and 2610 on the Games Index (GPU). The highest-scoring competitor, the HTC G2, scores 1045 and 1396 respectfully. DRockstar on IRC ran the benchmark on his Epic that has RFS, and scored 1133 and 2521. So, this benchmark tool actually performs fine on RFS. Amazing! Grab it off the Android Market!
Click to expand...
Click to collapse
That was great!
I scored 1147/2704 but i'm rooted/rommed.
the evo scored 700/910
razorseal said:
That was great!
I scored 1147/2704 but i'm rooted/rommed.
the evo scored 700/910
Click to expand...
Click to collapse
That EVO on 2.2? I would have expected it to score around 1000 at least. I wonder how it would score on EXT4 running CM6...
Smartphone benchmarks is a great benchmark.
Sent from my SPH-D700 using XDA App
Electrofreak said:
That EVO on 2.2? I would have expected it to score around 1000 at least. I wonder how it would score on EXT4 running CM6...
Click to expand...
Click to collapse
yup, it's a stock evo running whatever sprint updated for it
Scored 1257/2751 CM6 EXT4
Sent from my CM6 EXT4 Epic
1255p 2945g,Im running my ROM,how could I be faster then CM6? maybe not the best benchmark.
Sent from my SPH-D700 using XDA App
My Epic w/ Cmod's latest gave me 1115 and 2600
My wife has an Evo with CMods latest as well but only got 1089 and 1050, why so low on the second one?
My Epic scored 606\1901 in smartbench 2010. Weird... much lower productivity score than other people, but really high gaming score.
My Epic is stock.
EDIT: I ran it a few more times and watched it carefully.
603/1808
618/1954
633/1941
Seems I/O is pretty slow...
I'm just wondering why it matters? It's not like Android has a robust collection of high performance games.
razorseal said:
both running 2.2 (epic on dk28)
epic gets 991-1000 and the evo just scored 1241... wtf?!
the evo isn't EXT4 is it?
the epic is currently RFS... I'm having problems going to EXT4
Click to expand...
Click to collapse
Probably because she keeps her Evo in her bra and you keep your Epic in your pocket. It's a fact (check quadrant scores) that smartphones prefer boobs to guys hips 9 out of 10 days of the week. So obviously her Evo is happier and therefor performs better than yours. Do your Epic a favor and give him some booby time and watch those Quadrant scores rise!
+1,agreed and its been proven time and time again...
jirafabo said:
Probably because she keeps her Evo in her bra and you keep your Epic in your pocket. It's a fact (check quadrant scores) that smartphones prefer boobs to guys hips 9 out of 10 days of the week. So obviously her Evo is happier and therefor performs better than yours. Do your Epic a favor and give him some booby time and watch those Quadrant scores rise!
Click to expand...
Click to collapse
Can anyone report on some benchmark scores for the Xoom?
I found this one that Anandtech uses:
http://www.glbenchmark.com/download.jsp
That is a good benchmark for general openGL performance testing. Others are:
Linpack to measure floating-point rate of execution = generally useless score.
Quadrant measures overall system performance
Smartbench 2011 measures general system performance
The xoom scores very well. The scores in GLBenchmarks will seem low, because all tests are run at the native resolution on each device. So a phone with a 480x800 resolution and a tegra 2 will get a much higher score than the xoom with the same processor and a 1280x800 resolution.
Linpack is useless for dual-core devices, it only tests one core.
muyoso said:
The xoom scores very well. The scores in GLBenchmarks will seem low, because all tests are run at the native resolution on each device. So a phone with a 480x800 resolution and a tegra 2 will get a much higher score than the xoom with the same processor and a 1280x800 resolution.
Click to expand...
Click to collapse
Good to know! Hopefully, there will be some dual core benchmarks coming out soon.
Smartbench 2011 just added dual core support! I haven't tried it yet, only quadrant, but am anxious to see the differences.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app
js042507 said:
Smartbench 2011 just added dual core support! I haven't tried it yet, only quadrant, but am anxious to see the differences.
Sent from the most 'Epic' phone in the world! ...Using XDA Premium app
Click to expand...
Click to collapse
It runs in a tiny little window on the Xoom. Don't think this is a worthy benchmark for tablets.
Wow!
in SmartBench 2011 I got highest score there - 3895/2466. Some game scores were higher on other devices, but they were overclocked to hell.
I'm impressed.
My results are posted here (benchmark and quadrant) http://4pda.ru/forum/index.php?showtopic=173393&st=320#entry6752974
keitht said:
It runs in a tiny little window on the Xoom. Don't think this is a worthy benchmark for tablets.
Click to expand...
Click to collapse
Hi guys,
I am the developer of Smartbench 2010/2011.
Basically, I use device independent pixel system for rendering those bitmaps. For some reason, Honeycomb doesn't work so well with DIP. I need to look into why.
On the other hand, I don't believe there's any other benchmarks that spawn multiple symmetric threads for performing multi-core benchmark tests. All CPU tests are absolutely not affected by the screen size/resolution at all, so it shouldn't matter. IMO, I think its a bit premature to deduce that it is not a worthy benchmark from this observation.
And as usual, I am open to suggestions!
(Oh and Hi Arcadia, long time no see! )
Looking good, battery ok, feels smooth.
2.3.4 Quadrant
At last 2.3.4 seems to be very fast ! Quadrant score with out ext4 is 1600-1800 amazing!
PDA:XXJVP
MODEM:XXJVO
CSC:JV4XEN
Why are you all using Quadrant?
Run it 3 times and you won't even get the same score :| Pretty not reliant as a benchmark!
you won`t get same score cuz first time i like a cold start , it loades files etc.. second time you will get a better score
When you run 3dmark on a PC, you get the same (or around the same) score, same goes to a lot of benchmark software out there. Caching a benchmark goes against benchmarking itself...
t1mman said:
When you run 3dmark on a PC, you get the same (or around the same) score, same goes to a lot of benchmark software out there. Caching a benchmark goes against benchmarking itself...
Click to expand...
Click to collapse
Even that probably isn't truly indicative of performance. Nvidia and ATI both "optimise" *cough cheat* on benchmarks. Nvidia may blitz ATI in a certain game, but another game might be optimised for ATI. 3D mark also doesn't go into enough detail about what its testing (similar to Quadrant), which makes them both toys, because you don't get a breakdown. It doesn't tell you even basic stuff such as average random I/O speeds and very few benchmarks ensure that the test is run in a consistent fashion. You running the same test a second time leads to significantly better results, then caching is taking place, and the effect of caching should be added to the results too.
Benchmarks have unfortunately grown from an optimisation tool for developers, to a marketing tool for salespeople, and endusers who wish to boast. My suggestion, is that you should ignore them, and if you think the ROM feels nice, just use it. But, it seems most people are simply deciding on whether a ROM is nice AFTER they've seen the quadrant score, and that is a step backwards.
Its entirely possible to have dreadful real-world performance, but have the worlds highest Quadrant result (just like in a car, you might be able to drive 90km with 1litre of petrol. But if you only obtain that rate at 1km/h, its useless to almost everyone, especially if at 50km/h (normal speed), it starts gulping fuel like a ferrari).