I just read about a G1 getting a LinPack score of about 3.5ish. Most of the nearly 100% improvementwas attributed to using a rom with JIT. Since the G1 is very similar to the Vogue shouldn't we be able to get similar results.
I am currently getting 1.65.
D
-------------------------------------
Sent via the XDA Tapatalk App
If you thinks that's impressive, you should check out the new Froyo 2.2.
The Nexus One, which has 2.1 got a scrore of 6.5-7 MFLOPS, but with 2.2 it got 37.5 MFLOPS! That's an incredible performance increase.
I want 2.2, the G1 owners can keep their JIT compiler. Them fancy pants people. BTW, the article says that the HTC Hero averages a measly score of about 2 MFLOPS, so us getting 1.65 isn't bad. Though why the Nexus One gets 37.5 MFLOPS with 2.2 makes me wonder. It could be that 2.2 uses the FPU that's in the SnapDragonl, instead of the interger. If that's the case then our devices can only ever do ~1.65, cause they don't come with a FPU processor.
Though if JIT does give G1 owners a boost, then it'll certainly give us a boost. G1 doesn't have a FPU either. I'm also concerned about the 3D accelerator, as we get bad performance in some tests.
The G1 and Vogue share the same chipset--although their CPU is clocked at 528 Mhz, and ours at 400 (at least natively, that is.)
That probably accounts for the difference of 1.65 vs. 2 MFLOPs result.
If the Linpack test is to scale across all platforms, and we estimate an average 400% improvement in floating point performance, we can probably expect 6-8 in terms of a MFLOPs score on Linpack with Froyo.
Real-world applications (integer arithmetic) will not benefit nearly as well as FP arithmetic, because FP arithmetic is incredibly burdensome. However, perhaps an expected improvement of.. 100%, or 2x, is reasonable (depending). Programs with small rapid loops, etc. will see the most benefit. It'll be interesting to see how the Vogue performs.
In regards to graphics / the Vogue GPU:
I'm not completely up to speed on it, but I believe a primitive driver does work for OGL 1.0-based acceleration (Neocore?) but that's it; nothing more than 1.0 (which would explain why Live Wallpapers do not accelerate properly/crash, etc.)
I was under the impression the chipset between the Vogue and the G1/Hero/Eris was the same, and that if we simply used the driver from the G1/Hero/Eris's 2.1 ROM, we'd have full 3D acceleration.. but I don't think that's the case. There's plenty of smarter individuals here who would've ascertained the same thing, but nothing available.
I think (from a GPU perspective) we have official OGL 1.0 support and that's it.
The Kaiser, like the Vogue, uses the 400 Mhz Qualcomm chip. The difference between the chip in the Vogue/Polaris/Kaiser and devices like the G1 is Mhz and small changes done to the ATI accelerator. Though, I don't think the changes for the accelerator are major.
I have no idea about our Android setup. Is it using open source drivers? Is it using a driver taken directly from another Android device and modified, like from the G1?
I also wondered about the battery life using Android with 3D acceleration. Since Android is linux and linux open source graphic drivers are horrible and usually don't have any power management, could it be our poor battery life is due to the graphics driver?
Could it also be that the graphics driver from the G1 would work on our devices, but is a proprietary driver, and therefore can't be distributed? So instead we use open source drivers to avoid legal action?
If anyone knows the answers to these questions that would be great. I'm trying to wonder why my Kaiser with Android uses more battery life when not in use. Browsing the web or talking on the phone the battery life seems normal, but it's when it's idle that it consumes power twice as fast as Windows Mobile. To me it seems something isn't totally off when the device is in standby, and I'm thinking it's graphics related.
I've tested JIT enabled dalvikvm's on both Donut and Eclair. I never saw any noticable improvement in speed. I did however observe longer boot times and odd behavior from heavy memory intensive applications. For example, the browser sometimes doesn't launch when you have clicked it.
Give the JIT dalvikvm a try. Let me know if you experience anything positive on our vogues.
Here's a post for the G1 that uses JIT.
licknuts said:
The libdvm.so that t3steve cross compiled for the DROID at the time was for Android 2.0, the library works for with newer ROMs Android 1.6 that have some eclair pieces built into the kernel, CyanogenMOD has been using bits and pieces for a while now, if other ROM builders have been using his kernel and framework than a good chance it will work for your phone as well.
Click to expand...
Click to collapse
So, does that mean we just need eclair based roms, or is there more to that?
Dukenukemx said:
Here's a post for the G1 that uses JIT.
So, does that mean we just need eclair based roms, or is there more to that?
Click to expand...
Click to collapse
Eh, I'd just wait for Froyo, for an official JIT system designed specifically for use with the native apps in Froyo as well. Running an unofficial JIT compiler with older apps may cause some problems/force closes.. who knows.
Dukenukemx said:
I want 2.2, the G1 owners can keep their JIT compiler. Them fancy pants people. BTW, the article says that the HTC Hero averages a measly score of about 2 MFLOPS, so us getting 1.65 isn't bad. Though why the Nexus One gets 37.5 MFLOPS with 2.2 makes me wonder. It could be that 2.2 uses the FPU that's in the SnapDragonl, instead of the interger. If that's the case then our devices can only ever do ~1.65, cause they don't come with a FPU processor.
Click to expand...
Click to collapse
Without JIT (multiple test runs):
~ 1.65 MFLOPS for first 15 mins or so after startup
~ 2.33 MFLOPS after 15 mins after startup
Time to enable JIT and possible problems with apps, etc. it may cause probably isn't worth it to me.
You guys should check out this thread made by garringm from the Kaiser forum, if you wanna enable JIT. It should work, considering Kaiser users are using Vogue Android builds.
You'll need the Android SDK installed on your PC. Works with Incubus26Jc's Super Eclair and mssmison's CM 5.0.7 test 3. I ran linpack and got 3.3 MFLOPS.
I find at least for our vogues, linpack is not the best thing to judge by. It more calculations based which in most cases doesn't judge load times and the agility of our applications.
As I mentioned, I've used jit on a number of Donut and Eclair roms and although linpack may report a higher score the user experience in the speed dept wasn't improved.
Infact I found app load times to be longer with a jit enabled dalvikvm.
Are you sure the linkpack score isn't acting as a placebo?
Part of the issue is using (an unofficial) JIT compiler on a system not truly designed for it.
Froyo's compiler (along with Froyo's system) are designed to work with and efficiently use the new compiler, which means the best performance (and user experience) is going to come with Froyo, not Eclair/Donut/Cupcake with an unofficial JIT compiler.
I think we should just be patient--Froyo will be out soon, and we will surely port it to the Vogue, which will answer all of our questions.
myn said:
I find at least for our vogues, linpack is not the best thing to judge by. It more calculations based which in most cases doesn't judge load times and the agility of our applications.
As I mentioned, I've used jit on a number of Donut and Eclair roms and although linpack may report a higher score the user experience in the speed dept wasn't improved.
Infact I found app load times to be longer with a jit enabled dalvikvm.
Click to expand...
Click to collapse
Yes, the load times of applications are longer. Especially when applications are already loading slowly, this certainly doesn't help.
Are you sure the linkpack score isn't acting as a placebo?
Click to expand...
Click to collapse
Linpack is probably correct, as are the delays. I've played with emulators in the past, and I understand a bit about JIT. JIT is related to dynamic compilation, which a lot of emulators used in the past. Modern emulators like Dolphin uses JIT.
The idea is that instead of compiling data interpretively, it does it all in one shot, before the program executes. That way the program runs like it was made natively for the hardware. It would make sense that the applications have a delay in execution with JIT.
G1 owners don't have a problem with this since applications launch instantly on their phones. Running JIT for them makes no tangible difference. For us it's worse because we already have a 2-10 second delay to execute applications. This just makes it worse.
Another thing to consider is that many applications don't use MFLOPS, which is the FPU we don't have. Only 3D applications use that, and we don't use many of those. At least not yet. I'd like to try Quake 3 with it and see how it runs.
Related
Hi guys..
I sad Google developed 2.2 to improve snapdragon cpu and becuase of that the benchmarks shows 3X faster cpu on nexus,
will work 2.2 on galaxy like nexus ? or not for SGS cpu!
at all what you think about power of CPU/GPU in SGS on 2.2 ?
Is nexus cpu better than galaxy on Android 2.2 ?
The Galaxy's CPU/GPU is the best on the market right now and with 2.2 it should fix a lot of software problems with the SGS.
Actually can't wait for 2.2, and it's released around about my birthday!
When is your birthday
22nd September mate. You can buy me a Galaxy S as a spare if you want
well I have to see it first.
Guess Samsung finds a way to **** up the phone again i'm sure of that.
matty___ said:
well I have to see it first.
Guess Samsung finds a way to **** up the phone again i'm sure of that.
Click to expand...
Click to collapse
If it has rfs file format and TouchWiz, consider it ****ed up.
kgk888 said:
If it has rfs file format and TouchWiz, consider it ****ed up.
Click to expand...
Click to collapse
If froyo on the SGS sucks, then the chefs in here will cut it open and make it run properly and it won't matter what the FW was like when samsung sent it out. Also, TouchWiz is fine, even if it does have a dumb name.
I have been worried about this. The sgs line and droid line do not get over 15 in linpack with 2.2. I dont see the same increase in speed as I do with snapdragon based phones. I have read this is due to the snapdragon having 128 bit vs 64 bit something but cant find the forum post about this. The sgs line with 2.1 is still faster then a 2.2 snapdragon based phone but it must have the lag fix installed. Without the lag fix it is slower for sure. I will try to find the forum post about 128bit vs 64bit.
http://www.youtube.com/watch?v=gKsAUR61ByM
http://www.youtube.com/watch?v=ji49qFNxC4c
Edit: found the forum post
Originally Posted by Gimic26
Your question was answered already...it comes down to processor architecture. Qualcomm's Snapdragon platform and more specifically the Scorpion application processor, while being related to TI's Omap Arm series, has enhancements made by Qualcomm. The part of the cpu that handles the SIMD instructions has a wider pipeline, 128 bits vs 64 bits in TI's Omap. Scorpion also has a deeper pipeline to better handle all that data which I'd assume offsets some of the performance benefits a little bit.
As far as the difference between the two benchmarks, they are written to benchmark two different things. Linpack can run almost entirely within the SIMD/NEON portion of the cpu thereby showing off the enhancements made by Qualcomm. Quadrant stresses the entire core showing off total system performance showing that only in certain situations will Snapdragon outperform any other Arm based core.
shep211 said:
I have been worried about this. The sgs line and droid line do not get over 15 in linpack with 2.2. I dont see the same increase in speed as I do with snapdragon based phones. I have read this is due to the snapdragon having 128 bit vs 64 bit something but cant find the forum post about this. The sgs line with 2.1 is still faster then a 2.2 snapdragon based phone but it must have the lag fix installed. Without the lag fix it is slower for sure. I will try to find the forum post about 128bit vs 64bit.
http://www.youtube.com/watch?v=gKsAUR61ByM
http://www.youtube.com/watch?v=ji49qFNxC4c
Edit: found the forum post
Originally Posted by Gimic26
Your question was answered already...it comes down to processor architecture. Qualcomm's Snapdragon platform and more specifically the Scorpion application processor, while being related to TI's Omap Arm series, has enhancements made by Qualcomm. The part of the cpu that handles the SIMD instructions has a wider pipeline, 128 bits vs 64 bits in TI's Omap. Scorpion also has a deeper pipeline to better handle all that data which I'd assume offsets some of the performance benefits a little bit.
As far as the difference between the two benchmarks, they are written to benchmark two different things. Linpack can run almost entirely within the SIMD/NEON portion of the cpu thereby showing off the enhancements made by Qualcomm. Quadrant stresses the entire core showing off total system performance showing that only in certain situations will Snapdragon outperform any other Arm based core.
Click to expand...
Click to collapse
From what I've seen and read, the 2.2 builds for the Galaxy S do NOT have a JIT compiler enabled which explains the lower scores. The N1 got the huge CPU boost from having JIT enabled. That doesn't explain the Droid X's scores, but then again I haven't read enough about 2.2 running on the DX to see if it has JIT installed.
What're you think? I'll buy SGS 2.1 or wait for SGS 2.2 ?
It's very important to buy most powerfull phone.
I like Nexuse cus it's tested sucssasfuly in Android 2.2 and I'm gono love SGS if it will be better than nexus in 2.2.
Help me to choose better path )
Vogie said:
What're you think? I'll buy SGS 2.1 or wait for SGS 2.2 ?
It's very important to buy most powerfull phone.
I like Nexuse cus it's tested sucssasfuly in Android 2.2 and I'm gono love SGS if it will be better than nexus in 2.2.
Help me to choose better path )
Click to expand...
Click to collapse
I would wait at this time before purchasing an SGS if that's your concern.
Out of the box, the current phone/software is laggy and disappointing. If you're willing to hack it with some of the various fixes found here (I prefer samset with mimocan kernel), then you won't be unhappy with the phone, but there's no guarantee that Samsung will get FroYo right, and that if they do get it wrong that the devs here will be able to bring you a hot, non-laggy, super FroYo ROM before there's better, or at least comparable hardware done right by the manufacturer available.
That's no reflection on the devs here at all, I'm just thinking that Samsung won't release the firmware until the end of September, the devs will need a couple of weeks to make magic at least, and so now we're well into October. By October, the SGS will be a six month old phone. Six months is a very long time in the Android hardware world, and we'll likely see a landslide of new phones with faster CPU, maybe even dual-cores in the fall for the holiday season. The only thing the SGS will have over other phones at that point is the Super AMOLED screen by Samsung, since they're holding it all to themselves. I wouldn't be surprised if Moto or HTC try to kang the iPhone display tech for newer models if they can't get Super AMOLED for themselves.
In the android world it is nearly impossible to but a device that won't be out of date within at most a year and sometimes within 6 months.
Having said that, I don't see anything that will topple the sgs quite that soon. Although there is talk of dual core snap dragons, there has been nothing announced yet, and indeed the two new Desire handsets are still on the same chip.
I wouldn't expect to see anything that will have more raw power than the sgs until at least mid 2011. If there was anything closer than that it'd already be getting hyped.
If you keep looking at what is just over the horizon then you won't end up ever getting one, because there always seems to be something new out in a few months time. The sgs isn't prefect, but it beats the hell it of most anything that you'll be able to buy this year.
My humble opinion of course, but I think that if you want top end hardware, the sgs will serve you very well.
Sent from my GT-I9000 using XDA App
Based on your responses so far, I'd just get an iPhone 4 and be done with it.
There are a lot of people here and elsewhere who are perfectly happy with the device. I for one haven't installed the lag fix and I don't experience any lags, except for the situations below:
1. I'm trying to do something while there are several apps being installed/downloaded from the marketplace in the background. I think this will be resolved with the dualcore next gen CPU's.
2. Using LauncherPro, for all that is good and nice on this earth, I do not know why it took me 3 months before the option to change the shortcut on its drawer was shown to me. Imagine that, 3 months just to show the option to add a shortcut. Jeezus. I click on add shortcut and it took 3 months. Someone shoot me. I'm using ADW now and am very happy.
Out of sheer curiosity, why is it that you need "THE MOST POWERFUL PHONE"?
shep211 said:
As far as the difference between the two benchmarks, they are written to benchmark two different things. Linpack can run almost entirely within the SIMD/NEON portion of the cpu thereby showing off the enhancements made by Qualcomm. Quadrant stresses the entire core showing off total system performance showing that only in certain situations will Snapdragon outperform any other Arm based core.
Click to expand...
Click to collapse
The hummingbird core is widely recognized to be faster than the snapdragon core. Benchmarks do not tell you everything. Reference:
You might think that the Hummingbird doesn’t stand a chance against Qualcomm’s custom-built monster, but Samsung isn’t prepared to throw in the towel. In response to Snapdragon, they hired Intrinsity, a semiconductor company specializing in tweaking processor logic design, to customize the Cortex-A8 in the Hummingbird to perform certain binary functions using significantly less instructions than normal. Samsung estimates that 20% of the Hummingbird’s functions are affected, and of those, on average 25-50% less instructions are needed to complete each task. Overall, the processor can perform tasks 5-10% more quickly while handling the same 2 instructions per clock cycle as an unmodified ARM Cortex-A8 processor, and Samsung states it outperforms all other processors on the market (a statement seemingly aimed at Qualcomm).
Click to expand...
Click to collapse
Here is a GPU comparison for some of the leading smartphones:
Motorola Droid: TI OMAP3430 with PowerVR SGX530 = 7-14 million(?) triangles/sec
Nexus One: Qualcomm QSD8x50 with Adreno 200 = 22 million triangles/sec
iPhone 3G S: 600 MHz Cortex-A8 with PowerVR SGX535 = 28 7 million triangles/sec
Samsung Galaxy S: S5PC110 with PowerVR SGX540 = 90 million triangles/sec
Click to expand...
Click to collapse
Wait for G2 as nexus one is old news and i think they are winding down production. Frankly i love my sgs. Get it now cos frankly froyo is way over hyped compared to what sgs can do now with a lagfix
Sent from my GT-I9000 using XDA App
ickyboo said:
Wait for G2 as nexus one is old news and i think they are winding down production. Frankly i love my sgs. Get it now cos frankly froyo is way over hyped compared to what sgs can do now with a lagfix
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You can't really say froyo is over hyped, I mean its free, and beyond that its an incremental upgrade.
I don't see why anyone would be staying on eclair once official froyo drops, and you can't deny that it will bring a performance boost.
Now I doubt it will bring quite as much of a boost as it gave to the N1 until we get a few months of development to really get it running sweetly, but all the same its still not over hyped if I ask me.
With optimized ROMs and whatever fixes we need (cuz samsung WILL break something) I figure the sgs will shred the N1's new scores. I recon we'll see around 3k in quadrant.
Considering how far ahead of almost everything a lag fixed non-stock-rom sgs is now, we'll see something really special once froyo starts rocking our crotches.
Sent from my GT-I9000 using XDA App
The.Opethian said:
Based on your responses so far, I'd just get an iPhone 4 and be done with it.
There are a lot of people here and elsewhere who are perfectly happy with the device. I for one haven't installed the lag fix and I don't experience any lags, except for the situations below:
1. I'm trying to do something while there are several apps being installed/downloaded from the marketplace in the background. I think this will be resolved with the dualcore next gen CPU's.
2. Using LauncherPro, for all that is good and nice on this earth, I do not know why it took me 3 months before the option to change the shortcut on its drawer was shown to me. Imagine that, 3 months just to show the option to add a shortcut. Jeezus. I click on add shortcut and it took 3 months. Someone shoot me. I'm using ADW now and am very happy.
Out of sheer curiosity, why is it that you need "THE MOST POWERFUL PHONE"?
Click to expand...
Click to collapse
Why powerfull phone? ok i'll tell u:
Because I don't like to buy an expensive phone (like SGS) that power is lesser than a chipper phone (like N1) !
Because I'd rather a phone without stalling (lagging) to play games and running big applications. I will very gray if i'll se lagging/stalling...
Because I need a phone with a good support (it's enough, don't need mazing support). a phone with a clear (alive or nice) Future
JIT for Hummingbird should be promising.
High Mem
anyone got any idea on the high mem issue?... when i was browsing the Gmarket.com, i realize 305 total available memory is not enough for me... and the web page just closed....
Anything better than JPC froyo?
Sliced Bread?
No. Its the best IMO and I've tried 3 2.2 firmwares. With any luck Samsung will release the official one this month.
I hope so.
Jm7 is way better
Sent from my GT-I9000 using Tapatalk
my question is how come on the current froyo roms the linpack scores don't jump much... on the desire and nexus get somewhere in the region of 40 mflops...
Is it just cause they haven't properly optimised jit on the SGS yet?
Toast?
Sent from my GT-I9000 using XDA App
Sorry the HK 2.2 is by far better than JPC...
Ibanez33 said:
my question is how come on the current froyo roms the linpack scores don't jump much... on the desire and nexus get somewhere in the region of 40 mflops...
Is it just cause they haven't properly optimised jit on the SGS yet?
Click to expand...
Click to collapse
In another thread i pointed out the same thing as you are, because i read somewhere else that HTC had to do very little job to optimize JIT for Snapdragon, having google done that with AOSP.
They replied to me saying that first Froyo FWs for Desire and N1 reached ~ the same jump from Eclair Build: 8 to 14 Mflops. Only later, with progressively better setup, they reached the 40 Mflops zone.
It could also be that JIT, the feature that most of all power up Linpack benchmark, is completely disabled in Froyo builds like JPC. I asked how we could check this, but no-one answered properly to that until now.
I've just upgraded from JM2 to JPC and for sure JM2 is better. JPC has poor responce on finger gestures and is sometimes slow. I hope these problems are solved in the final release. I'm downgrading today!
clubtech said:
Sorry the HK 2.2 is by far better than JPC...
Click to expand...
Click to collapse
Care to elaborate and cite the differences?
Stefanauss said:
In another thread i pointed out the same thing as you are, because i read somewhere else that HTC had to do very little job to optimize JIT for Snapdragon, having google done that with AOSP.
They replied to me saying that first Froyo FWs for Desire and N1 reached ~ the same jump from Eclair Build: 8 to 14 Mflops. Only later, with progressively better setup, they reached the 40 Mflops zone.
It could also be that JIT, the feature that most of all power up Linpack benchmark, is completely disabled in Froyo builds like JPC. I asked how we could check this, but no-one answered properly to that until now.
Click to expand...
Click to collapse
Oh right.. I assumed JIT was enabled but poorly implemented. 14 Mflops without JIT it pretty good! can't wait to see what happens.. Can't wait for a better leak or a proper release..
Ibanez33 said:
Oh right.. I assumed JIT was enabled but poorly implemented. 14 Mflops without JIT it pretty good! can't wait to see what happens.. Can't wait for a better leak or a proper release..
Click to expand...
Click to collapse
JIT is enabled in JPC. We might see a 20 in the final release if we're lucky, but definitely nothing more than that. The Snapdragon phones apparently have a dedicated FPU which enable them to reach such ridiculous scores. Droid X, Droid 2 and all other 1GHz non-snapdragon phones get sub 20 linpack scores on Froyo.
Sent from my GT-I9000 using XDA App
ed10000 said:
JIT is enabled in JPC.
Click to expand...
Click to collapse
How do you know that for sure?
It's a proper question, it's not that i don't believe you.
Stefanauss said:
How do you know that for sure?
It's a proper question, it's not that i don't believe you.
Click to expand...
Click to collapse
I didn't think it was.
EarlZ said:
Care to elaborate and cite the differences?
Click to expand...
Click to collapse
- Does not mess with you efs folder. That alone makes the HK version a winner.
- Excellent GPS reception and lock.
- Excellent battery life
- No lag
- I only had ONE FC with the HK JP2, unlike JPC.
Stefanauss said:
How do you know that for sure?
It's a proper question, it's not that i don't believe you.
Click to expand...
Click to collapse
There are messages about it in the log e.g.
I/dalvikvm(18078): Jit: resizing JitTable from 8192 to 16384
D/dalvikvm( 2477): JIT code cache reset in 5 ms (1048428 bytes 19/0)
we'd need samsung to optimize the jit for their hummingbird, while it might not reach N1 scores it could probably get quite a bit better
but having seen how good samsung code is, well, that just isn't happening
ps: i agree i got less issues with jp2 hk than jpc as well, especially the lags and FC's and *battery life* (it's like double time)
I've been running JPC for 5 days now, and it's great. I have no desire to switch back to an Eclair rom. I still don't have a lag fix installed and don't feel I need to. I'm also not getting any FCs at all.
What's the deal with everyone wanting massive Linpack scores anyway? What software requires that grunt? Movies run perfectly, games are fast, and most other software wouldn't even touch the capabilities of either the Snapdragon or Hummingbird processors.
If it's a pissing contest you want to win against an N1 or Desire owner, simply load up Real Football 2010 and show them how comically fast it is, since it was written for their phone and no frame limiter was appied.
For me it's not about the benchmark per se.
JIT is one of those great Froyo features, and it can massively impact performance (it's clear, for instance, that Snapdragon vs Hummingbird architecture has very little percentage impact on Linpack, it's all about JIT optimization, like 15 to 40 just tuning JIT), not just in some pointless floating point benchmark.
Nevertheless, JIT is an issue where Samsung has to put its hands on code-wise, and they definitely proved during this childhood of this phone that they can very very very much suck at that.
So this benchmark could be helpful to understand how much effort Sammie is putting into Galaxy S Development, maybe.
I had a Samsung Moment and most of the rom descriptions included the Mflop scores. I sold it and got a Hero and I've noticed pretty much no one lists or talks about Mflop scores? Is there a reason for this, is it not important since the Hero is so slow anyways?
The fastest score I've seen was with the new AospMod rom 5.6. Do any of the 2.1 roms compare?
reckoner13 said:
I had a Samsung Moment and most of the rom descriptions included the Mflop scores. I sold it and got a Hero and I've noticed pretty much no one lists or talks about Mflop scores? Is there a reason for this, is it not important since the Hero is so slow anyways?
The fastest score I've seen was with the new AospMod rom 5.6. Do any of the 2.1 roms compare?
Click to expand...
Click to collapse
I think it's because no one here really cares about it. Mostly because it doesn't matter. Most of us on the hero boards are more concerned with important stuff like stability, and coming from a moment and calling the hero slow is a case of the pot calling the kettle black. ;-)
reckoner13 said:
I had a Samsung Moment and most of the rom descriptions included the Mflop scores. I sold it and got a Hero and I've noticed pretty much no one lists or talks about Mflop scores? Is there a reason for this, is it not important since the Hero is so slow anyways?
The fastest score I've seen was with the new AospMod rom 5.6. Do any of the 2.1 roms compare?
Click to expand...
Click to collapse
MFlops is an arbitrary cpu scoring system much like Bogomips for Linux and you see it posted on almost every roms OP. The problem is that its affected by tons of stuff and just because aospbot posts a 5.6 doesn't mean thats what you'll get, you might be running a ton of widgets and facebook sync and other stuff.
CM6 also got a 5.6 or so and I've seen 2.1 sense rom also post a high scores like this. You should use it yourself and determine what is a good score on your phone under normal conditions and then use that as a bases for scoring other roms on YOUR phone.
Mflops are usually calculated by how many Floating Point operations it can calculate per second (usually pi to some exponent), while Mips is how many Fixed point operations it can calculate a second.
So pretty much ignore it unless your running it on your phone.
user7618 said:
I think it's because no one here really cares about it. Mostly because it doesn't matter. Most of us on the hero boards are more concerned with important stuff like stability, and coming from a moment and calling the hero slow is a case of the pot calling the kettle black. ;-)
Click to expand...
Click to collapse
Come on the moment has an 800mhz processor that can be overclocked and the same amount of RAM as the Hero (288). It's faster, but that doesn't mean it's better. I prefer the Hero.
reckoner13 said:
I had a Samsung Moment and most of the rom descriptions included the Mflop scores. I sold it and got a Hero and I've noticed pretty much no one lists or talks about Mflop scores? Is there a reason for this, is it not important since the Hero is so slow anyways?
The fastest score I've seen was with the new AospMod rom 5.6. Do any of the 2.1 roms compare?
Click to expand...
Click to collapse
Mflops is still used, but it is no longer a primary measure of a phone's capabilities. Most people use Quadrant to determine a phone's performance, as that incorporates 2D and 3D graphic performance in addition to calculations. But I've heard people use BenchmarkPi, CPU Benchmark, etc. It all is really quite irrelevant if your phone is fast enough and performs well enough for you; posting scores of any type is really just a digital pissing contest.
So I just watch that honey comb video and they said its o optimized to use dual core processor. But all these tegra two phones only running froyo .
So does out means there its no point of getting these phones untill honeycomb for phones comes out .
raydm said:
So I just watch that honey comb video and they said its o optimized to use dual core processor. But all these tegra two phones only running froyo .
So does out means there its no point of getting these phones untill honeycomb for phones comes out .
Click to expand...
Click to collapse
Even if froyo is not optimized for dual-core you will still have an advantage with dual-core, just look at some benchmarks and you will see that the tegra2 will score much better than ordinary singel-core at same speed, so no need to wait.
But the performance will be even better when the device is runing honeycomb.
real world performance is we actually need here.not just some benchmark numbers. Mytouch 4g overclock to 1.4ghz can beat those numbers easily.
So why spend soo much money on first generation 2x processors.
Just saying.
raydm said:
real world performance is we actually need here.not just some benchmark numbers. Mytouch 4g overclock to 1.4ghz can beat those numbers easily.
So why spend soo much money on first generation 2x processors.
Just saying.
Click to expand...
Click to collapse
With that opinion why even ask the Q you did?
Compare only stock to stock and OC to OC my friend..
As far as I know multi-core-support is included since 1.6. This means that if an application uses multiple threads u get a performance gain up to 100%. So Froyo is sufficent in that case.
Hower, newer android version bring additional optimizations to speed things up on multi-core-devices to tha tabble (especialy for application that either only use one thread or can't max out all cores). In 2.3 it is a multithreaded filesystem, in 3.0 it is the dalvlik-layer for executing java-based apps.
Anandtech just completed their review of the 2X and they show that Android does in fact know that you are using a dual core processor. The results seem to be especially noticeable in the browser (which is great news for me as i surf a lot on my htc hero and this is always a pain!).
Having said that, Honeycomb (and whatever it's phone counterpart will be) will put further emphasis on dual core tegra2 use.
As for real world in app differences... it's going to be like froyo install to sd.... this is something that developers need to do.. android can't force any one app to use multi-cores.. the app needs to be coded to take advantage of it.
This phone is kinda marketed to people who want to future proof themselves. So while real world experience may not differ currently with single core processors, it will change once android start's using both cores, well as two cores, instead of one core and a maid.
Simple poll. I am curious to see who uses JIT and who has it disabled? If you answer, please explain why you do or do not use JIT. Just thought I would get people's different input on this
i used to have it enabled but had seen no positive outcomes, just more lag.
but that was when i was running CM6... i havent tried it on CM7 yet.
I know JIT on Sense 2.1 was disastrous for the most part. Have stayed away from it for the most part.
JIT on CM7 is actually very stable, however I observe absolutely no improvement or noticeable change in performance anywhere.
Then again, people also claim a smoother experience when "Allow purging of assets" is unchecked, even thought it is meant to improve performance of low memory devices like ours... YMMV, I guess.
My question is, what are the supposed benefits? Scoring higher on a particular benchmark score and thats it? I agree. It doesn't seem to make my phone any smoother, if anything, it makes it more laggy.
I've been using jit since the days of Ic3 rom and damage's roms as well. I think it just improves data. No speed on the phone just how the phone complies data. I think. But from my time on here if you can't overclock to 768 and run stable then I'd recommend avoiding jit.
Yea its Me Again With The
Modified Hero
In aosp 2.2 I would get an extra 20 or so on my quadrant score with JIT enabled. In gingerbread I haven't seen any improvement at all. I leave it disabled because I heard it uses more ram to speed things up.
I use JIT and I always have since installing custom ROM images. There's a lot of hearsay left over from long before I joined xda-developers that says it causes instability. But this is probably more to do with the original way JIT was brought to the Hero.
The latest official software for the Hero is built from Android 2.1. JIT was not introduced into Android until 2.2. So as far as I know, the original method to implement JIT on the Hero was to hack it into the official software. This is likely where the instabilities were found.
I've been using JIT since dabbling with CM6 (and its derivatives), and I've never seen any negative effects. I do, however, always decrease my VM heap to 24m and enable compcache at 18% when using JIT. Not doing so MAY cause JIT to starve the phone of memory, which could be another source of the instabilities you've seen mentioned.
Some people say JIT isn't necessary because its effects are only noticed in benchmarks such as Linpack. This, simply put, is false. JIT is always going to offer a performance increase. Now, depending on how you use your phone, the increase may not always be very noticeable, but that doesn't mean it's not there. And the less time the VM spends using the processor, the more battery life you're going to see. That's an angle that isn't always addressed when JIT is discussed.
My advice is to leave it enabled as long as you don't specifically see any issues with it. Our sister phone of sorts, the Droid Eris, now has it enabled by default in CM7.
Thanks jasonmaloney, I always prefer hearing answers from people with technical know-how such as yourself. On a CM performance related note, what is your opinion on people reporting better performance with "Allow purging of assets" disabled?
c00ller said:
Thanks jasonmaloney, I always prefer hearing answers from people with technical know-how such as yourself. On a CM performance related note, what is your opinion on people reporting better performance with "Allow purging of assets" disabled?
Click to expand...
Click to collapse
I was actually the one who submitted the patch to enable it by default. I've only ever heard of specific issues in relation to ADWLauncher, which, in my opinion, shouldn't ever be used in the first place due to the numerous better-written alternatives.
But I'm starting to wonder whether it has anything to do with the GPS problems people have been seeing.
All I really know for sure is that the graphics subsystems in CM7 for the Heroc are screwed up, and that they're probably going to be that way even when CM7 is finalized.
EDIT: If anyone can find compelling evidence that having it enabled is causing issues, I'll revert the patch and make it disabled by default.
jasonmaloney said:
All I really know for sure is that the graphics subsystems in CM7 for the Heroc are screwed up, and that they're probably going to be that way even when CM7 is finalized.
Click to expand...
Click to collapse
Is that a good or bad thing? Yes the words used dictates it's meaning, but what would have been the plus factors if it were squared away?
oohaylima said:
Is that a good or bad thing? Yes the words used dictates it's meaning, but what would have been the plus factors if it were squared away?
Click to expand...
Click to collapse
The most glaring example of a problem is seen in running Neocore. None of the textures show up.