http://forum.xda-developers.com/showthread.php?t=1010807
Would this work for the Nexus S?
Not necessary for the nexus s because that read ahead variable is already set at the more optimal value. That speed fix is only necessary/applicable to older kernels which had a different default which was much smaller.
Related
Anyone know the optimal value of VM heap size for Nexus S?
It's default value is 32, but Galaxy S GB update set the value to 64.
Is 64 okay to Nexus S?
You can set the value to anything you want. It just says how much memory one app can use at maximum.
So there is no real need to raise it until apps start complaining about not enough memory.
They never complain. Android just shuts them down. So it depends on your usage when you notice that one app got killed while you started another bump up your heap.
Sent from my Nexus S 4G using XDA App
obsanity said:
So it depends on your usage when you notice that one app got killed while you started another bump up your heap.
Click to expand...
Click to collapse
Sorry, but that's not how it works. The memory usage of one app has nothing to do with the usage of another. We are talking about the maximum memory allowed for (in general) ONE app.
When your apps are well-behaved, i.e. well-programmed, then the max heap size should not make any difference, as long as it is big enough for the app to run in the first place.
It is more likely that the higher your max heap setting is, the fewer apps can run in parallel, because android will keep VMs with large heaps around.
Could anybody please comment on the VM HEAP SIZE since I am noticing that the latest 4.2.2 has 128MB in this setting!!! My device is still the same and i have not started using some crazy games with lots of requirements. Is this 128MB good for my device or not??? To me it sounds like it is not.
Could anyboyd tell me if they went back to the original 32/64MB?
I know most are going to say if you dont know what it does dont mess with it. Just have been reading alot but curious how it may vary from phone to phone?
If I may I will list some basic stuff.
SD card boost, I have read about this and it depends on the speed of your card, so what is the standard card rated at or what do you set it at?I set mine at 1024.
Auto memory manager, 8,10,16,32,64
Sysctl tweaks, Have read alot about this over the years with different phones and it is never really clear so dont ever touch it.
Build. prop tweaks
I have my lcd density at 235, vm heap at 55m so far and dont really use wifi.Have thought about trying to adjust the vm heap.
Cpu slider I have tried both conservative and ondemand but havent decided. Ofcourse if you read the basic stuff as to if you want performance or save battery it explains it.
Last I have also read about configure apps to sd card or internal memory. Some of the non important apps I dont use all the time went straight there.
Well let my education or slamming begin.
I'd say that vm heap is too high. I know it's subjective, but I don't think you'll gain anything over about 48, and most rims i've downloaded on 1ghz/512 phones seems to be set at 42 or 48.
Sent from my SCH-I510 using Tapatalk
ilovesoad said:
I'd say that vm heap is too high. I know it's subjective, but I don't think you'll gain anything over about 48, and most rims i've downloaded on 1ghz/512 phones seems to be set at 42 or 48.
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
Depends. Some purposes need it higher. Team GummyCharged just released a patch to fix TSM Parts hot boot issues that increased the heap size to 80, and it seems to have done the trick. Last time I tried GC, I had multiple hot boots a day...haven't had one on the new settings yet.
I just saw something yesterday when I was on imoseyon page any had it about 80. Was doing alot of reading all over. Will play around a litte to see what may work.
what should i have this set on its default at 32m atm and wanted to know what everyone else has theirs at
boroboy69r said:
what should i have this set on its default at 32m atm and wanted to know what everyone else has theirs at
Click to expand...
Click to collapse
I set mine at 64m.Some even set it as high as 88m on the new ICS Roms.. They claim it improves speed and performance.You can experiment with different values and see what works best for your Rom.
The higher you set it the more battery you end up using.
I have mine set to 64 as most people that I know do. Seems to be a good balance.
Well, my tf101 is transfering data to the internal storage (/sdcard) at very slow speeds. Antutu is reporting Write speed of 4.5-8MB/s and Reed speeds of 19-22MB/sec.
This seems pretty bad in general, but my Rezound with similar specs is getting ~20MB/sec write speeds and it just says ">50MB/sec" Read speeds and doesn't even bother to give an actual value...
anybody know of any scripts, tweaks, mods, anything to improve the situation?
it is beause of the partitioning in honeycomb. The more data you have the lower the speed you can mess around with system tuner to get a better value though
mrevankyle said:
it is beause of the partitioning in honeycomb. The more data you have the lower the speed you can mess around with system tuner to get a better value though
Click to expand...
Click to collapse
Can you clarify at all? How does the partitioning differ? I was getting speeds like that on my Rezound when it was running Android 2.3.4 Gingerbread, and now its running 4.0.1 and still getting much faster speeds than my TF. How is the partitioning in Honeycomb somehow affecting the transfer speed if a previous version of Android didn't exhibit this issue?...
a.mcdear said:
Can you clarify at all? How does the partitioning differ? I was getting speeds like that on my Rezound when it was running Android 2.3.4 Gingerbread, and now its running 4.0.1 and still getting much faster speeds than my TF. How is the partitioning in Honeycomb somehow affecting the transfer speed if a previous version of Android didn't exhibit this issue?...
Click to expand...
Click to collapse
You could try slightly bumping up the read ahead on each memory block might help performance not so much speeds
blck0-1024kb
blck1-2048kb
Would be a start atleast hope it helps
Sent from my Transformer TF101 using xda premium
hey guys. was wondering what is the best cache size for the internal memory? I believe by default it is 2048. I get an option ranging up to 6144. should I go for the max? Is the improvement significant? and does it affect battery life? Thanks guys!
azreen91 said:
hey guys. was wondering what is the best cache size for the internal memory? I believe by default it is 2048. I get an option ranging up to 6144. should I go for the max? Is the improvement significant? and does it affect battery life? Thanks guys!
Click to expand...
Click to collapse
Why don't you test it yourself amd tell us?
https://play.google.com/store/apps/details?id=ales.veluscek.sdtools
You can go higher than specified on the stock setup of 2048, and you might get an increase in certain scenarios, but keep in mind that the read ahead is mostly effective in its nature of fetching that chunk of data for a purpose. Not just to get filled up with wasted data you aint gonna need anyway. It can be fine for speeding up eg. Browsing your pictures with Quickpic, but you probably waste a good chunk of cachespace that could be more usefull for data you actually need in a fast sequencial read scenario.. Most of what advices for the readahead Ive read from the old dogs on xda points at a 512kb set, as a balance between effectiveness and wasted cache, atleast on phones, but it could be a tad different on our tabs as they are already at 2048 probably for a reason. So digg in and let us know how you fare
Omnius
Sent from my A510 using xda app-developers app
I was wondering why people keep on asking to try it by myself, It doesn't hurt to ask before trying right?
and yes I have tried increasing it and I don't see any improvement with the read speed(since write speed is not going to be affected as been told in a forum topic)
I believe omnius001 was right, it could have been set to 2048 for a reason or two, so increasing won't do better, let's just stick to 2048 then thanks for replying anyway!
azreen91 said:
I was wondering why people keep on asking to try it by myself, It doesn't hurt to ask before trying right?
Click to expand...
Click to collapse
Well, as we say, no guts-no glory It really doesn't hurt anything.
The problem is that all stock Acer tabs suffer from a very poor IO, mostly when it comes to DB writes and other IO functions. Running a simple Quadrant benchmark at standard setting will affirm this. Just look at the IO results. The poorest of any device out there, and poorest by a lot!
Not sure whether this is because of the "noop" scheduler Acer insists on using. Generally, this is an ok scheduler, however BFQ handles things better in my opinion.
Tweaks to improve IO performance have been around for awhile. Generally, as in the Iconia Tab series, it involves some changes in ramdisk, and not the kernel itself. Unless Devs add the BFQ scheduler, which requires a kernel rebuild.
I have a modified kernel (701), unfortunately, never got a chance to test it, before the CWM recovery borked. If I compare to the 501, it should increase IO performance by 400%, more inline with other devices.
Why Acer in 2 years, hasn't improved IO performance when they easily can, well, it escapes logic.
MD