So far this is the highest I have seen:
dalvik.vm.heapsize=38m
Would increasing or decreasing help speedwise? Would it be stable to, for example, go to 46m?
From what I understand heapsize is how much memory you can allocate to any given application at a time. With Froyo builds there's so much memory I don't see why increasing the heapsize would be so dangerous.
Related
Just wanted to start a thread to see what you guys use for advanced CPU settings. Do you OC (and how much)? What governor do you use? Do you have JIT enabled? If so, what's your VM heap size? Do you use compcache? And most importantly, what differences have you noticed by trying different settings?
Right now I'm OCing to 245/710 on GSB 1.2 with no JIT or compcache and using the smartass governor, and my phone is running better than it has in a long time. I tried GSB with JIT and compcache and noticed a definite slow down.
If you're not using JIT, you're not getting any benefit that I can see of having a 2.2+ ROM. My Linpack scores go up about 50 to 75% when I turn on JIT.
Most of the time, I have the clock set at 604/245, with a screen off at 528/245. For the Froyo/GB ROMs, I always have JIT, compcache at default, vm heap at default, governor at smartass.
For Eclair ROMs (running Zanfur's kernel) I generally have the same clocks, ondemand governor, no JIT. Sometimes I set the minimum at 19.2 on Zanfur's kernel and it still seems to run fine - it tends to depend on how fast the battery burns.
GSB 1.2
Min 245
Max 604 - 768 depending on usage
Gov. Interactive
Compcache off
JIT on
VM heap 24MB
Surface dithering off
Lock home in memory off
Lock messaging off
Also been using xtr's cache2cache.
Sent from my GSBv1.2 using XDA App
GSB 1.3
Min 245
Max 748
Gov. On Demand
Compcache 10%
JIT on
VM heap 32MB
Surface dithering off
Lock home in memory off
Lock messaging off
Noticed a slow down running Compcache at 18%(default). If my battery starts getting low, I'll change my max to 528.
with GSB 1.3
Min 245
Max 710
Gov. On Demand
Compcache 26%
JIT On
VM heap 32MB
Surface dithering off
Lock home in memory on
Lock messaging off
I am using XTR's Cache2Cache script which helps me maximize my space seeing as I have a massive amount of apps installed (107) and my caches are very high. I'm running at around 30-34MB free space. If I didn't use Cache2Cache i'd be at 0-5MB free and i'd have all kinds of memory issues. =-) XTR rocks!
I dont get any lag, not yet at least. home screen doesn't reload either.
Izeltokatl said:
lock home in memory on
Lock messaging off
I am using XTR's Cache2Cache script which helps me maximize my space seeing as I have a massive amount of apps installed (107) and my caches are very high. I'm running at around 30-34MB free space. If I didn't use Cache2Cache i'd be at 0-5MB free and i'd have all kinds of memory issues. =-) XTR rocks!
I dont get any lag, not yet at least. home screen doesn't reload either.
Click to expand...
Click to collapse
I've been getting that homescreen reload thing, too. I assume saving the "lock home in memory" fixes that?
oceanminded said:
Just wanted to start a thread to see what you guys use for advanced CPU settings. Do you OC (and how much)? What governor do you use? Do you have JIT enabled? If so, what's your VM heap size? Do you use compcache? And most importantly, what differences have you noticed by trying different settings?
Right now I'm OCing to 245/710 on GSB 1.2 with no JIT or compcache and using the smartass governor, and my phone is running better than it has in a long time. I tried GSB with JIT and compcache and noticed a definite slow down.
Click to expand...
Click to collapse
245/748 gsb 1.4 JIT enabled compcache at 26% performance no slowdown that i noticed.
EDIT: Autokiller at Ultimate and the majority of my user apps on the SD card only ones with widgets and those that dont work on SD card on internal. Memory normally stays at about 40-50
i am using GSB 1.6 running setCPU at 748max and 240min and it is completely stable. It has had no noticeable effect on battery life.
Is anyone having issues w overclocking to 806 w interactive. Running tazz froyo gb and siedio
stk, I have issues overclocking to 806 period.
JIT should be on with any 2.2+ device.
Compcache off, our cpu is too weak to do any extra work like that.
VM heap size at 16, where it garners top performance.
Sleep profile: 19min, 480max
powersave bia, 40
up threshold 98
wakes up just fine
any suggestions?
many feedbacks now are annoyed with getting low ram..
resulting lower performance of cm7...
hehe..thanks..
low ram=faster app lauching. that is good
huh?
im having about 70mb free ram..
it goes robotic..haha
What are you running on you ace?
Get the V6 supercharger script by zepplin of course
Set CPU min and max to 800 Mhz
Also set CPU gov to 'performance'
Actually default settings are good enough
My settings: V6Supercharged, compache disabled, JIT enabled, surface dithering disabled, purguing of assets enabled, VM heap size 48m
SAUROM with build.prop tweaks, nothing else flashed through CWM
Hi I noticed that when over about 525mb or RAM usage on our device it starts to increase launcher lag and general lag across:
GO Launcher
ADW Launcher
TW Launcher
I tried different CPU governers:
Smartass2
Ondemand
Power Save (dur dur dur)
And right after I turn it on within 5 mins this is my RAM:
http://www.box.com/s/65b898b945607334c5b5
http://www.box.com/s/6cc0ab0a29bd003e9dc6
Can I reduce the amount of memory the apps marked with RED use?
Can I remove the ones circled in GREEN safely by deleting the apk?
How much memory do we want to keep free at all times?
Thanks in advance!
fixed 2nd link sry
zeppelinrox who makes scripts told me to use less dalvik heap size and i tried it,,are phones are 128mb,,,i turned mine down to 64mb and it seems to run alot more smoother now,,,I've noticed both roms have 128mb which is too much and not needed for this device..That's why i keep my stock with only a overclocked kernel and just add my own build prop tweaks....
wish777 said:
zeppelinrox who makes scripts told me to use less dalvik heap size and i tried it,,are phones are 128mb,,,i turned mine down to 64mb and it seems to run alot more smoother now,,,I've noticed both roms have 128mb which is too much and not needed for this device..That's why i keep my stock with only a overclocked kernel and just add my own build prop tweaks....
Click to expand...
Click to collapse
Thanks for the response. I will look for an app that can help me modify this and post back if it uses less memory.
memory optimizer root works for adjusting more aggressive settings it free too....
wish777 said:
memory optimizer root works for adjusting more aggressive settings it free too....
Click to expand...
Click to collapse
i just checked it out but actually going to roll with RAM Manager Free or RAM Manager Pro seems awesome, thanks for your help as you were the only one that replied lol.
Hi guys...I don't know where to post this...anyway...
looking in a post full of tweaks for android i saw that some tweak change dirty_ratio (setting it to 90) and dirty_background_ratio (setting it to 70)...now, I'm noob with android, but I use linux and I think that these settings are to manage the behavior of the kernel regarding the write on the disk of the dirty pages (on linux I set this value high when I'm with the battery, that reduce consumption by reducing I/O operations)...but setting high values (such 90 and 70) on devices like smartphone is equally efficient?I have some doubt...maintaining dirty pages in memory reduce the I/O frequency, but doesn't occupies RAM?And, in addition, if the kernel accumulates many dirty pages in memory and then writes all to disk we will unable to perform I/O operations while it is writing dirty pages, and this translates in some strange and seemingly inexplicable lag IMO...Am I wrong?
Please, help me to understand better this fantastic OS...
EDIT:
Ok..continuing explore /proc/sys/vm I noticed that setting that values so high (dirty_ratio and dirty_background_ratio) we say to the kernel that it has to keep dirty pages in memory until they expires (dirty_expire_centisecs set to 200) or until the pdflush wakes up and writes all the dirty pages to disk (dirty_writeback_centisecs set to 500)...so basically the only things that we do by changing that values are that we limit IO operations without affect the performance...
Hi there,
i have a Oppo Find7s, which is a 3GB RAM device, and i'm on a Marshmallow ROM. Unfortunately Marshmallow RAM management is aggressive.
So many apps are reloaded again if the are accessed. Also there is always around 800MB free RAM. I thought on Android(Linux) free RAM is bad Ram:
I played around with predefinded LMK values (Kernel auditor) but i'm not very satisfied with the result.
Does anyone have good LMK values for a 3 GB RAM device. I think the LMK values have to be manually adjusted.
Thanks .....