Database Develop

Performance

Okay, another question that makes me feel kinda dumb.
How can I improve my N1's performance?
Specifically, how in the world do I get my nexus even close to the N1's I see on Linpack's "Top Devices"?
I'm running diet_2.6.33.2.hybrid_avs_925mv_OC with cyanogen 5.0.6. I can get 7.778 MFLOPS. Honestly, I don’t even know what that means. All I know is that I want more. Or do I? Does it even make that much of a difference in everyday usage?
I've noticed that in the JIT thread under development they talk about getting up to 17 MFLOPS, but no one really explains what JIT is or does. Just that it's unstable and that if your not sure what it is, you don't need it.
I can benchmarkPi in 2790 - how in the hell do I get it lower? Under the rom description of some of the top 50 they mention JIT and experimental kernels, but there's not much room for more than just the generic names of them. Where do I get these magical roms and kernels? Do I even want them? Are they so unstable that they can only be used to gain geek cred on some benchmark lists and once they hit the "high score" they explode in flames? Do I need safety goggles before I flash the update.zip?
Seriously though, I know I'm not the only one with these questions - so any info would help. And do me a favor, please do not respond to say that if I don't know - I don’t need to know. At one point, you didn't know either. No one was born with this knowledge.
I know there is a very bright person on here that is willing to take a couple of minutes to shed some light on us simpletons. I'd like to thank you in advance. Thanks.

Even if you get higher linpack scores, you will barely notice any difference in your devices performance... That's why I tend to ignore it. If its possible to get faster than Cyanogen ROMs (not in terms of linpack) I don't know how different things would be.. im curious about how quick Froyo is though.
Oh and have you searched, Jit has been covered in more places than just xda developers, several times it has been discussed I believe.. while using it, my Linpack scores did get into the double digits though - but this (not even that noticeable actually) speed increase was not worth the random reboots, and such. When Jit is stable though, it will be quite nice.. hopefully Froyo has it.

Linpack number did not make any differences in overall usage . Now, I am using my own UV kernel and setcpu max freq to 500MHz.. only... but, I still able to get 26.8 fps in Neocore's 3D benchmark. Playing games, 3D or not, still smooth and fluid.
I also waiting for Froyo and hope we can get even efficient and fast OS.
TQ.

Is there a JIT enabled rom for the Vogue?

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.

Quadrant sucks, howto properly bench our devices?

I'm creating this thread based on what i read here: http://briefmobile.com/cyanogen-demonstrates-quadrants-flaws
I'd really like to know what lagfix gives me the best results and i lost my faith in quadrant. Are there any decent alternatives? Most benchmarks i know are only good for testing cpu performance...

Its not fair to say that quadrant sucks, and particularly I don't like that the article seems to be implying that the lagfixes that a lot of us are running are simply artificially inflating the SGS's score. The SGS has the best harware on the market crippled by bad firmware, and tbh I think its the lag fix that has allowed the hardware to be reflected in quadrant scores.
Anyway, quadrant doesn't suck. Its not perfect, but it does help you determine for example, how different ROMs on the same device compare for performance, as well as showing off things like GPUs that often don't get seen.
However it just runs a series of tests and weights the results accordingly. Particularly, the I/O seems to be given a lot of weight and so can be nobbled to increase the score. However, as anyone who has experienced excessive lag on their SGS can attest, it also works the other way. Without the lag fix, the SGS is a very pedestrian device, as the ~1000 quadrant scores tell you, while with the fix it FLIES.

Actually, some people are saying they notice no difference with the lag fixes it seems. And I've also seen forums full of people saying they can hear the difference between WASAPI/Exclusive audio and shared audio in Windows. Amazingly, out of the dozens of people trying to destroy me and demand it was implemented, none of them were willing to blind test (they were all just willing to say "it's obvious"). How many people here running the lagfix, have run any kind of blind test, or test with predictable steps to demonstrate a difference? Please, raise your hand people, because there is a huge difference between "it seems lag is gone" and "Lag is verified gone".
Quadrant is a guide, it doesn't test interactivity, and it only tests a few operations. It's similar to how a browser can pass ACID3, but have terrible compliance to new standards. Because people became so convinced of benchmarks accuracy, Nvidia and ATI started optimising for benchmarks.
Normal SSD's are also blazingly fast on benchmarks initially, but if they don't have TRIM, their performance drops significantly. That's another example of something benchmarks don't accurately test (because the testing is incomplete).
Use it to get a general idea of how the phone performs (although, specs might be more useful in some cases), but you probably need profiling and a predictable list of steps to diagnose the lag exactly. Run benchmarks which test according to the types of applications you are planning to run (if you play 3D games for instance, use a 3D game benchmark). But don't rely on them exclusively to tell you how well a device performs, because only running the applications and testing them yourselves can tell you.

LostAlone said:
Its not fair to say that quadrant sucks, and particularly I don't like that the article seems to be implying that the lagfixes that a lot of us are running are simply artificially inflating the SGS's score. The SGS has the best harware on the market crippled by bad firmware, and tbh I think its the lag fix that has allowed the hardware to be reflected in quadrant scores.
Anyway, quadrant doesn't suck. Its not perfect, but it does help you determine for example, how different ROMs on the same device compare for performance, as well as showing off things like GPUs that often don't get seen.
However it just runs a series of tests and weights the results accordingly. Particularly, the I/O seems to be given a lot of weight and so can be nobbled to increase the score. However, as anyone who has experienced excessive lag on their SGS can attest, it also works the other way. Without the lag fix, the SGS is a very pedestrian device, as the ~1000 quadrant scores tell you, while with the fix it FLIES.
Click to expand...
Click to collapse
But do you really think that one-click-lagix or whatever is that much faster than mimocan's one (like 2800 vs 1800)? I don't think so...

andrewluecke said:
How many people here running the lagfix, have run any kind of blind test, or test with predictable steps to demonstrate a difference? Please, raise your hand people, because there is a huge difference between "it seems lag is gone" and "Lag is verified gone".
Click to expand...
Click to collapse
*raisehand*
Predictable steps to demonstrate a difference:
1. Use 2 SGS, firmware of your choice
2. One with, say, 1 Click Lag Fix - the other one stock
3. Now for the test, perform simultaneously:
3.1. Open Market and go to "Downloads", update an app, close.
3.2. Open Contacts, quickly switch to favourites, dial Number. Drop call. Exit.
3.3. Open Messaging, conversation of your choice, quickly switch the writing language, write, send, exit.
3.4. bla bla goanforeva
Now if you don't notice an improvement there and in many other cases you most certainly have done something wrong.
If you are saying people are just being placebo-ed you are implying that everybody else besides you is unable to tell a real difference. Think about it, maybe it's the other way around.

When I got my device it came with the Asian JG4 firmware I think and I used it for 48hrs as a point of reference for this so called "lag" I updated my firmware to the latest we have and found zero difference in terms of performance ( same 2 day usage ) decided to flash my device with JM5 and used it w/o a lag fix for 2 days, notice a very slight improvment on how fast the inbox/contacts can open and then did a fresh flash with lagfix 2.x installed I didnt NOT notice any performance difference but I am always open and welcome to any lagfix that is stable,safe and fast ( in that order ) right now I have JG8 installed w/o lag fix and its very snappy, I still want to install a lag fix for this even if i dont see/feel any performance difference at all.. thats just me.. Now im wondering w/c lag fix is the most stable and safe.. stability/safty > speed
EDIT:
Also I believe it could be possible that certain versions of lagfixes work better with certain versions of firmware also, its all about getting the perfect combination.. altho my question still stands on w/c is the safest lagfix heheheh

Well actually i gave up on benchmarks.
To me the whole user experience is more important. If apps open instantly and the phone runs smooth then it's fine with me. I did notice some firmwares are better then other ones.
Right now i'm running JM1 (rev 3) with CFLagFix1.80 installed which makes the phone very stable and running smoothly so right now i'll stick to this firmware until a proper GPS fix is released or until Froyo is released.

Phandroid said:
*raisehand*
Predictable steps to demonstrate a difference:
1. Use 2 SGS, firmware of your choice
2. One with, say, 1 Click Lag Fix - the other one stock
3. Now for the test, perform simultaneously:
3.1. Open Market and go to "Downloads", update an app, close.
3.2. Open Contacts, quickly switch to favourites, dial Number. Drop call. Exit.
3.3. Open Messaging, conversation of your choice, quickly switch the writing language, write, send, exit.
3.4. bla bla goanforeva
Now if you don't notice an improvement there and in many other cases you most certainly have done something wrong.
If you are saying people are just being placebo-ed you are implying that everybody else besides you is unable to tell a real difference. Think about it, maybe it's the other way around.
Click to expand...
Click to collapse
Lol I think you didn't understand my question... I'm sure that these lag fixes all work, no doubt about that. But which of them is faster? For that i can't rely on quadrant i'm sure...

JIT for DroidX

I posted this on another forum with little avail... I didn't want to clutter this one up... However, without a clear answer, and actually very little intelligent conversation that resultant in my reluctance to actually respond... I have to resort to placing this here.
"
So I have been playing around with the OTA 2.2 and decided to run linpack, I noticed an incredibly low score for froyo, (around 12-14) in comparison to the average Froyo score of 30-40. Figured I would play around in the build.prop, noticed JIT was not mentioned. Did they leave out enabling JIT for the Droid X froyo? Or am I missing something here...
"
This was posted back on the 27 of September, since then I have poked around more and still have found little to answer my original question. Seriously, is it possible to have Froyo without JIT enabled... I know better than anyone to take benchmark scores with a grain of salt, it just seems a little odd to me. As a side note, Java performs worse than my Droid Incredible did, while the snapdragon is indeed a better computational processor, it quite significantly outperformed the Droid X in both Linpack and Java (I don't believe in quadrant enough to even run it...) which it truly should not...
Anybody have any reasonable input?

Where did you ever get the idea that 30-40 is a reasonable score for JIT enabled phones? Because of the N1? As I understand it, the N1's processor offloads the JIT compiler, vastly speeding up MFLOPS (Millions of Floating Operations Per Second) which is GREAT for linpack benchmarks, but its really not important as far as real world performance.
Stop taking so much stock in meaningless benchmark tests. MFLOPS are a terrible way to compare device speeds. Especially when you bring a phone into the mix that has a special way of handling MFLOPS.
Apps that test video decoding/encoding and FPS are much more likely to give you a better idea of real-world phone performance
If I'm wrong in any way people, please feel free to enlighten me.

LexusBrian400 said:
Where did you ever get the idea that 30-40 is a reasonable score for JIT enabled phones? Because of the N1? As I understand it, the N1's processor offloads the JIT compiler, vastly speeding up MFLOPS (Millions of Floating Operations Per Second) which is GREAT for linpack benchmarks, but its really not important as far as real world performance.
Stop taking so much stock in meaningless benchmark tests. MFLOPS are a terrible way to compare device speeds. Especially when you bring a phone into the mix that has a special way of handling MFLOPS.
Apps that test video decoding/encoding and FPS are much more likely to give you a better idea of real-world phone performance
If I'm wrong in any way people, please feel free to enlighten me.
Click to expand...
Click to collapse
With all do respect, it is responses like yours that anger me slightly (albeit very slightly...). I specifically stated in my post that I do not hold benchmark tests in any regard, in fact I despise them... Quadrant in particular is so incredibly broken that a simple trickery in database write caching can bloat your score to such ridiculous heights, that it is not worth even turning an eye to any more. I did state however, that the benchmark did catch my attention enough to make me investigate the JIT compiler on our device. The only comparison I had to make were with 2.1 devices, in which JIT was referenced in the build.prop. I am unaware how it is enabled in 2.2, hence the question. I specify that as a common score as the Devour, EVO, Nexus, Droid Incredible, Samsung Galaxy I900, and iPhone (yes, i said it...) all see scores in the 30's through linpack. I am not giving those scores any relation to performance, because as I stated in my original post, "I know better than anyone to take benchmark scores with a grain of salt"... but thank you for not reading the full post, and discrediting my post *moderately angry face* (but more jokingly).
But in all seriousness, those phones showing the benchmark, while not giving an impression of performance, did give an impression, or rather a relation, to JIT. While JIT does not give performance increases in the amount shown through benchmarks, the performance gain is significant in some areas, and I would be heartstrucken if they managed to provide Froyo without JIT to the Droid X. I was just looking for confirmation that JIT is enabled, or a way to check. If I cannot get a straight answer around here, I will discover it sooner or later on my own. I am not even sure it is possible to have Froyo without having JIT enabled, but it caught my attention enough to have it investigated.

Sorry, i did not mean to upset you by taking time out of my day to TRY and answer your question. (Twice now)
Yes, JIT is enabled.
Edit:
And I guess I should have noted that I wasn't really talking DIRECTLY to you when I mentioned about people should stop taking so much stock in benchmarks. My bad. That was for others who happen to read this.

You guys... let's play nicely.

FWIW I've heard that JIT is in fact enabled...but the reason it's not very prevalent is because JIT was designed to be very efficient mainly with the qualcomm snapdragons and such..not the TI omap. I could be wrong but I believe this is why...and I believe the X still performs just a smoothly as those snapdragons which score higher on the benchmarks (which, I know, is not the question at hand, just giving my 2 cents).

LexusBrian400 said:
Sorry, i did not mean to upset you by taking time out of my day to TRY and answer your question. (Twice now)
Yes, JIT is enabled.
Click to expand...
Click to collapse
Clearly you did not catch the sarcasm and joking tone I had in my writing, my apologies, I updated it to more clearly represent it ;-). Truly was not trying to sound angry, more sarcastically hurt... And I take time out of my day to help people all the time as well... look back at my posts, this is one of the few questions I've asked... I'm not a fan...
I understand, I know who you are... You've done a lot for the community... Thanks... I appreciated the incite and really didn't even care about the comment, I was more just joking about it in that I stated how I don't actually take heed to benchmark scores. Regardless, JIT was an area I am not really all that familiar with, and appreciate the answer. I play more on the system level as I am a Linux Server Administrator and deal mostly with script writing over actual compiling. Sorry if you thought I was taking shots at you ;-)
EDIT: FYI this isn't the first time people have thought I was being an ass to them... I am... what do they call it... anti-social... I just come across that way, I don't mean to however. I think I have actually had this conversation with another Developer on another forum, it ended in him admitting to the same problem... I think we then had crumpets and tea... well maybe not the crumpets and tea, but the rest is true...

Its all good captain taco, I truly wish I had a better answer for you.
the Jit ON/OFF switch, in my other phone, is in the build.prop. However, I do not see it in the Droid X build.prop
From 2.1 to 2.2, the linpack jumped over 6 points. And seeing that its just a software update, I guess you could say I'm blindly assuming that JIT is enabled, but I also want you to take note that apps that have trouble running in conjunction with JIT, also did not perform well until they were updated to work with it.
I can say in 100% confidence and (barely) educated guess, that JIT is in fact, enabled.
Have a good day Taco

LexusBrian400 said:
Its all good captain taco, I truly wish I had a better answer for you.
the Jit ON/OFF switch, in my other phone, is in the build.prop. However, I do not see it in the Droid X build.prop
From 2.1 to 2.2, the linpack jumped over 6 points. And seeing that its just a software update, I guess you could say I'm blindly assuming that JIT is enabled, but I also want you to take note that apps that have trouble running in conjunction with JIT, also did not perform well until they were updated to work with it.
I can say in 100% confidence and (barely) educated guess, that JIT is in fact, enabled.
Have a good day Taco
Click to expand...
Click to collapse
Sounds good to me, that's about as good of an answer as it gets. Thanks

Is there not a way to get a real answer to this question? Motorola should be the source I suppose. Anyone have contact info or access to a Moto android software engineer?
Can someone be motivated to ask Moto if jit is enabled in 2.2 on the X?
We can speculate all we want.
Sent from my DROIDX using XDA App

Izord said:
Is there not a way to get a real answer to this question? Motorola should be the source I suppose. Anyone have contact info or access to a Moto android software engineer?
Can someone be motivated to ask Moto if jit is enabled in 2.2 on the X?
We can speculate all we want.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I feel as though his answer gives fair evidence that JIT is indeed enabled. It's likely just placed elsewhere, after all it was just a single line calling JIT in the build.prop, it could have been placed in any of the startup files, could be in the boot.img for that matter. I really haven't searched through all of the init scripts, and after reading LexusBrian400's response, I likely won't, I feel pretty assured it is enabled.

read the blog about 1/2 way down on nenolod.net titled "how to improve user performance on android phones"

mcsinfl said:
read the blog about 1/2 way down on nenolod.net titled "how to improve user performance on android phones"
Click to expand...
Click to collapse
Have you tried this yourself???

mcsinfl said:
read the blog about 1/2 way down on nenolod.net titled "how to improve user performance on android phones"
Click to expand...
Click to collapse
I believe that blog was meant for pre 2.2 android. I am not even sure we are able to make that change in 2.2, though do not hold me to that.
/etc/sysctl.conf is not a file in our system, and at the end of his post the author quotes "Update: Disabling NORMALIZE_SLEEPERS on Android 1.6/2.0/2.1 is a good idea."
Edit: Scratch the above, further digging in the comments section of that particular post:
nenolod says:
July 22, 2010 at 4:56 am
@moo: these are all scheduler enhancements made upstream already. Froyo already has them.
Click to expand...
Click to collapse

CaptainTaco said:
I believe that blog was meant for pre 2.2 android. I am not even sure we are able to make that change in 2.2, though do not hold me to that.
/etc/sysctl.conf is not a file in our system, and at the end of his post the author quotes "Update: Disabling NORMALIZE_SLEEPERS on Android 1.6/2.0/2.1 is a good idea."
Edit: Scratch the above, further digging in the comments section of that particular post:
Click to expand...
Click to collapse
The rubix rom has that mod in it. In the changelog, where he mentions "tweaks by nenolod" The Sleepers mod is what he is talking about. I just ran the code from nenlods blog and it went through fine. (on rubix) Sometimes sysctl.conf is in the /sys file I believe. I think thats what nenlod said, I talked to him last night about it because I was curious.
Anyway, it works on Rubix

JIT is enabled without a doubt.
The only reason there was a line in the build.prop was because it was a homemade JIT compiler for our phones. This is probably embedded into Froyo.

Just wanted to confirm, I watched a logcat today for about 15 minutes, JIT came up several times.
Download Alogcat and have a looksee for yourself.
It may take a while, but it'll come up for sure.
CONFIRMED
/end thread

LexusBrian400 said:
The rubix rom has that mod in it. In the changelog, where he mentions "tweaks by nenolod" The Sleepers mod is what he is talking about. I just ran the code from nenlods blog and it went through fine. (on rubix) Sometimes sysctl.conf is in the /sys file I believe. I think thats what nenlod said, I talked to him last night about it because I was curious.
Anyway, it works on Rubix
Click to expand...
Click to collapse
i had a little trouble finding the sysctl file on my phone but it turned up in the /system/bin .
i like to keep a copy of any file i change, incase anything goes awry and I tried viewing the contents of the file on my PC but it was just a bunch of cryptic symbols. Is there a way to see what the file contains?
and thanks for the logcat confirmation of jit

drewden123 said:
FWIW I've heard that JIT is in fact enabled...but the reason it's not very prevalent is because JIT was designed to be very efficient mainly with the qualcomm snapdragons and such..not the TI omap. I could be wrong but I believe this is why...and I believe the X still performs just a smoothly as those snapdragons which score higher on the benchmarks (which, I know, is not the question at hand, just giving my 2 cents).
Click to expand...
Click to collapse
This is exactly true. The OMAP doesn't see nearly the gains from JIT as the hummingbird/snapdragon does.

EXT4 worth it?

Hi, so after cm rooting i noticed there is also an ext4 upgrade...is this worth it and will I have data lose during the change? Im on 2.3.3 and am wondering if it is really worth it! Ed

are you kidding me?
besides that this post should not even be in this forum (try Q & A) there are hundreds of other posts and threads discussing this topic if you only use your -(0-0)- !

Yes and no
It may have some advantages but as for what I'm not sure but as for nay major advantages I would say no. I'm still using EXT2 and my benchmarkes are still 1900+. I've tried almost all the other lagfixes and found no real advantage. The only thing I hate about custom kernels with lagfix is the secondary samsung splash screens and custom splash screen. They kill the post time.

I would say it isn't as worth it as what people say. First thing most people do after converting their filesystem is run quadrant. It's possible that improved quadrant scores don't translate to real world performance though.
Even worse, running quadrant actually engages the placebo effect so you walk in with a more positive impression. Meanwhile, I don't recall ever seeing anyone from the EXT4/EXT2 i9000 community running blind tests, and neither development community has actually shown any evidence formal testing has been performed. All the arguments seem to be based around quadrant and PC testing. If methods like this were applied to clinical testing, every drug would pass
Honestly, give both a try, but do it blindly.
Why Quadrant may be wrong
This is just a bit of background why Quadrant's scores may not reflect real life performance. Until we check the actual ratio's of Quadrant, and compare with actual usage ratio's though, we can't identify how "real" it's scores are.
Consider a benchmark which produces 1 final score. It may be calculated by:
[MAX TIME - Time to read 1000mb] + [Max time - time to write 1000MB]. In this case, both scores contribute to 50% of the final score, which can be worth 2x MAX Time.
Scenario 1: Time to read/write is both the same
Scenario 2: Read time is 1% shorter than Scenario 1, but write time is 1% longer. Both will have the same score in Quadrant..
Scenario 3: Read time is 5% longer than Scenario 1, but write time is 50% shorter. Scenario 3 will get the best score
Which one is ACTUALLY faster though. The benchmark-toting individuals will claim Scenario 3 is faster, because of the score. HOWEVER, that may be incorrect. Consider the following:
If a user reads 100x more data than they write:
1) Clearly, faster read scores are more important.
2) The BEST filesystem will be Scenario 2, despite being equal last.
3) Scenario 1 will be mid place
4) The scenario with the best score, will actually have the WORST performance.
5) A drop in 1% read performance would need a HUGE increase in write performance to actually be faster.
Until we have an idea of how accurate Quadrant REALLY is, run your own tests, and do so without knowing which filesystem is running. High quadrant scores may boost your e-penis size, but as you can see, it is theoretically possible for the scores which are produced to score slower performing filesystems more highly than faster ones. Disappointingly though, a decreasing number of users/developers at XDA these days are actually interested in the truth, and simply in not being wrong.
Even worse, the community for some reason seems VERY anti-RFS, and wont give it a chance regardless. It might be a LOT better than it used to be. Either way, it seems to be good enough for me.
Ignore the theatrics and run a blind test. That's the only way to determine what is ACTUALLY faster.

monkeytennis said:
Hi, so after cm rooting i noticed there is also an ext4 upgrade...is this worth it and will I have data lose during the change? Im on 2.3.3 and am wondering if it is really worth it! Ed
Click to expand...
Click to collapse
I guess you mean CF root right? Will just answer the data loose question. No you shouldnt. But do a backup before. Its fast and easy (if you are on CF root that is)
If its worth depends on you? You experience any lag on rfs? Phone slow?
ramrod54 said:
It may have some advantages but as for what I'm not sure but as for nay major advantages I would say no. I'm still using EXT2 and my benchmarkes are still 1900+. I've tried almost all the other lagfixes and found no real advantage. The only thing I hate about custom kernels with lagfix is the secondary samsung splash screens and custom splash screen. They kill the post time.
Click to expand...
Click to collapse
@ramrod54 , where did you get ext2 support on JVK? And what the?
What samsung splash screens and custom splash? What rom and kernel are you on? And what lagfixes? And we both know quadrant score doesnt matter does it ?

Yes, it's worth it. Some things (Android Market, Gmail) works really MUCH faster then on rfs.

Unrealwolf said:
Yes, it's worth it. Some things (Android Market, Gmail) works really MUCH faster then on rfs.
Click to expand...
Click to collapse
Hrm, I've never noticed a difference. Market is slow on any room, hell market.android.com is slow too. Gmail always worked fast for me, on any rom.
Personally, I don't see or feel the point in using anything but rfs, but I suppose if someone has half a bazillion apps installed, then maybe an alternative filesystem might be better.
I say try it. If you notice a difference, good for you. If you don't, then stick with rfs.

What about battery performance ? from what I have read, battery performance is also better with RFS.

I always use ex4, its not as needed now on gingerbread but I just prefer the file system...it is better than RFS...but RFS has improved a great deal so you may not noticed that much difference, the rom may become a little smoother..You wont get data lose because of ex4, maybe the way the kernel is built...dont forget that 2.3.3 gingerbread is still beta and without the source code for the kernel you cant expect great things yet, although chainfire has done some amazing work and now we can change the file system using his app....works really well.
Also regarding battery, the difference in performance is such a small margin that its not even an issue.
What alot of people aren't aware of is that the Nexus S for example uses ex4 file system as default straight out of the box
Its not just a lagfix for the galaxy s, its a very good file system too...
Just a side note on Quadrant, ex4, ex2 will trick the app...if you buy the pro version, you will see how much the file system stretches on the bar...Quadrant is more for fun....or HTC

Think it´s worth cause rfs slow down your system after a while