So I'd been using JIT on my Evil Eris ROM (and I'd used it with a few others) and I was getting scores of 5.1~ mflops. Here are some things I noticed.
While I had first enabled JIT it was glitch free. I can safely say at this point that any "speed increase" I'd noticed was likely placebo or at least admissible.
JIT is amazing, but it's amazing for Froyo. The way a JIT compiler works is that it precompiles information into code that is more easily read, causing slight lag to begin and increasing overall performance. The thing they had to do with froyo is optimize just about everything to stop the lag and to make JIT worthwhile.
The other reason is that despite removing sense and eventually using the Universal JIT and basically doing everything to make it stable JIT began to show problems. It was absolutely stable for a very long time but if I left my phone on for a few days or I started installing new programs/ a new launcher it would get glitchy and laggy. This likely goes back to what I said about JIT really being much better for Froyo. It came to the point that I felt slower than before I rooted.
Now that I'm not on JIT I can also overclock higher. Before I was limited to 768mhz and if I went over it was an instant crash. Now with JIT removed I'm up to 787, I can do 806 but it only lasts a few minutes before it freezes up but it's proof to the concept that I can overclock much higher. I get consistently 3.4~ mflops.
I do realize that I while on JIT I got a large increase in mflops but in my experience I am performing better without it. I think that when Froyo ROM's come out JIT will be much better implemented.
tl;dr: JIT ended up causing lag, I can overclock higher without it, I'm just as fast/faster without it.
note: For something like a game JIT may help you much more than just scrolling around since the game will be precompiled and then run more smoothly but in my experience (with Zenonia mostly) there was no improvement and occasionally I would in fact lag more.
Just thought I should say this to everyone.
Kind a sounds like steroids, ya you get muscle and look cool but there are side effects
Yeah and JIT was made for Froyo, not for the other ones. Froyo was heavily optimized, they spent a ton of time just making everything work as well as possible so that the JIT wouldn't actually be detrimental. So while JIT does increase MFLOPS and performance it can cause a lot of bugs and slow downs because it's trying to compile information that isn't optimized for it.
Hm. I think I'll try disabling JIT for a while too. I might prefer the quicker load time over any supposed increase in performance. I haven't had much buggy behavior, but I have had some restarts and wonder if they're caused by JIT or just overclocking in general.
I've found overclocking surprisingly stable without JIT. It's incredible that I can overclock to 806mhz now with glitches and 787 is absolutely stable...
Looking back I realize now that JIT had slowly degraded, I started off overclocking without it to 787 and as I turned it on it began to get very glitchy with 787, eventually freezing immediately with it. I wouldn't be surprised if the restarts you're having are due to JIT in combination with overclocking.
good post +1.
the devs don't say anything about this in their threads, thats if they even know it or have experienced it themselves so i'm not blaming anyone.
good to know so i can at least eval it for myself. thanks.
I think JIT might have been interfering with my Swype. Maybe it's doing too much "just in time" compiling and not enough "ahead of time" compiling. But anyway, yesterday I switched back and forth several times between using JIT and not using JIT, but didn't change anything else, and I definitely noticed that Swype was more responsive without JIT. With JIT enabled, I kept having to retype things because my tracing path would skip over parts; it was choppy. Without JIT it's smooth as silk and therefore accurate again.
I think a lot of the problem is that apps also aren't made to use JIT yet, all of the developers made apps for non-JIT phones first... you see a LOT of problems in phones that have background apps (setcpu, autokillers, etc) when they have JIT enabled. I think anyone who read up on JIT when it was announced will see mentions of the google dev's saying "We really really streamlined the phone to make use of the JIT".... obviously they're remarking that JIT without streamlining and "light" OS is a bit of a waste. JIT on my Froyo ROM (CM6) is very much more stable. If anyone's interested I did some benchmarks for JIT here:
http://forum.xda-developers.com/showthread.php?t=726038
Found this in the Hero forums, and it obviously applies to the Eris as well:
illogic6 said:
http://forum.cyanogenmod.com/topic/880-jit-wont-make-your-phone-super-fast/page__p__7910?#entry7910
Notice this portion of the post: "CPU intensive tasks get faster, but at the cost of RAM."
The way Darchstar explains it is that our phones cannot sacrifice that RAM once our phones have been bogged down with installed apps. He doesn't plan to include JIT by default when CM 6 goes final for HeroC and that's why.
Click to expand...
Click to collapse
Yes well you can decrease or increase the amount of RAM that JIT will use (heap size) and increase stability or decrease it. I understand why it's default off, it makes sense especially since a lot of programs aren't made to use it *cough pandora cough*
I'm running Cyanogenmod 6 froyo, did you test the effects of turning on and off JIT on this ROM?
Yes, like I said JIT was literally made for Froyo ROMs, and you can quite clearly see that when you hear the devs who created it talk about it in google conferences and such, they had to do a lot to get JIT to work well without creating huge slowdown. Compilers are almost ALWAYS a bad idea because of their nature and because if information isn't made for the compiler it ends up doing more harm than good.
Froyo is streamlined to work with JIT without causing slowdown so I would highly recommend using the JIT compiler with Froyo.
Hungry Man said:
Yes, like I said JIT was literally made for Froyo ROMs, and you can quite clearly see that when you hear the devs who created it talk about it in google conferences and such, they had to do a lot to get JIT to work well without creating huge slowdown. Compilers are almost ALWAYS a bad idea because of their nature and because if information isn't made for the compiler it ends up doing more harm than good.
Froyo is streamlined to work with JIT without causing slowdown so I would highly recommend using the JIT compiler with Froyo.
Click to expand...
Click to collapse
What about the Compcahe? Idk what it even does ahah
I turned JIT and surface dithering off. Phone runs smooth and no force closes.
surgeon0214 said:
What about the Compcahe? Idk what it even does ahah
Click to expand...
Click to collapse
Compcache can speed some things up. I enabled it on a SenseUI ROM a while ago and had TERRIBLE, crashing results until I turned it off, at random.
I can confirm that JIT's make Swype crash sometimes. I can do a 100 fast-swype word experiment (which, I do a lot of 'texting', so this experiment happens every day), on days I have JIT on, Swype randomly disappears. (it is set to restart itself after 5.0 seconds, so don't worry). With JIT off, it only does its normal random crashing (when I accidentally hit the Swype key while it's thinking of what words I just swyped, for example -- just the known crash bugs).
JIT day was yesterday, for example (I'm experimenting with JITs because of this thread) - and Swype crashed more than 10 times (I stopped counting by the time I was at the bar for two hours, -- don't drink and swype!)
Non-JIT day was today, and Swype has not crashed 1 time (despite writing a few very long emails in a passenger seat and some serious texting).
Monday is a JIT day, and I'm pretty confident based on my findings, that these have a huge impact on Swype.
I'm just using SenseUI for the weekend (for reliability/etc, because I'm 'On Call' for work), but if my findings prove my theory WRONG, I'll edit this post and note that.
But in general, yes, I agree, JITs mess with Swype. Not to a point of usability, but to a point that, the late person might think Swype is unreliable (unknowingly).
Compcache is your processor compressing the information that is stored in your RAM to increase the total amount of RAM that you can use per program. This can increase performance by letting your programs use more RAM but it can also decrease performance by increasing the time that the CPU has to work on compression. For the Eris I don't suggest Compcache unless you're overclocking to at least 710mhz and if you're on a Froyo ROM I don't suggest it at all since you should have plenty of RAM already.
What VM Heap Size are you using pkopalek? Smaller heap sizes are more unstable, you may find swype is more stable at 24m if you're at 12 or 16. 24m is the point where sense becomes stable (sorta) with JIT.
I rooted my Samsung Galaxy S and there was a great improvement in perfomrance with a filesystem fix as well as access to custom Roms via ROM manager. What benefits will I get with rooting the Streak? Is there any big performance boost I can get out of it?
with mine being rooted used steakdroid and found the could increase cpu speed, battery was lasting longer and not bogged down with dell ui which had various apps running
Just having the device rooted itself is half the fun. Being able to do whatever you want on it with no restrictions!
Personally I don't do anything that really needs a performance boost.I think it's quick enough in my opinion. Will probably be looking into Underclocking to increase battery performance. Would still be interested in your results though if you try.
I've played around with the performance settings a little bit but haven't really found much improvement in gaming.
Anyone found a good combination that maximizes the performance of our NT?
I guess I'm the only one who tinker's with settings!
What ones are working for you?
How does DRH compare to our best Froyo Roms? I'm mainly concerned with stability and fluidity (ie, top-end gaming or video speed isn't as important as moving within and into-and-out-of apps). With the second core up and running in ICS, is DRH now our most consistent daily driver if we don't need the camera or the mic?
I've been running Clemsyn's Beastly combo for a while now, and it's incredible, but it lags on the two programs I use the most: Pulse and Dolphin, and for whatever reason its wifi connection is a little wonky for me. I've been following the DRH progress pretty closely, and my trigger finger is getting really itchy wanting to flash it. However, I'm about to travel a lot this summer and will need my GTab for work (word processing mainly), so I need it to be stable and reliable while I'm away from my desktop and can't monkey around with it if I need to.
So, community, what say you? Should I make the jump now, should I hold off until they roll out the 3.x kernel, or should I stick with Beastly?
(All of this, by the way, is asked in complete humility, knowing that I'm playing around with incredible work by incredible--and incredibly generous--people!!)
I have not used the Froyo ROMs, having installed Flashback and then DRH.
I like DRH, it is fast, I still get kernel panics when the tablet hangs and/or reboots. It surfs *very* well, esp with the different launchers.
I have noticed not all games work with ICS. I love Madden NFL but it won't run.
Froyo is still the smoother experience imo, however the ICS kernel is catching up very quickly. For me its definetly good enough for a daily driver, only minor anounces to deal with at this point. Fosser2 has even hinted that he may have a working camera and mic soon. I think in another month or two ICS will easily hold its own against the Froyo roms. Give it six months and we wont even be talking about anything but DRH's ICS kernel for the gtab.
I found the ICS to be maddeningly slow, switched back to C and C and it is a pleasure again.
I load a lot of apps, and when I want to use them I do not expect slow loading and constant warnings flashing on the screen. I hope ICS gets there but IMO not there now.
As the title says, has anyone tried SuperCharger on the Galaxy S3 yet? There have been quite a few recent updates for full ICS support without having to go through any extra hoops. I could SWEAR by SuperCharger when I was on the Epic 4G and it'll be interesting how much more we can push the Galaxy S3 with the tweaks starting to popup.
I think it was a must have on the the OG Epic, however, I've been very pleased with the S3 with no changes from stock, even with power saving limiting the CPU. No lags, no stutters, etc.
I am not convinced it is needed. I played with it quite a bit on my G2x and it made little difference in the benchmarks. The GS3 has a lot more horsepower than the G2x so I would well enough alone until some bullet proof tweaks come our way. I have made the mistake in the past of jumping on unproven tips and tricks and regretted it.
Nothing wrong with SuperCharger and I thank the dev that created it, but I think it may have a bigger impact on phones with fewer resources and power than the GS3.