About Build.prop original Dalvik virtual machine setting and adjusting

System/build.prop original Dalvik virtual machine setup is like this.

1.dalvik.vm.heapstartsize=8m (indicates that the initial size assigned to the application after it is started is 8m)
The amount of memory allocated here affects the overall system's use of RAM and the fluency of the first time the application is used.
The larger the value, the faster the system consumes RAM, but the faster the application opens.
The smaller the value, the more RAM is left on the system, but the program will slow down after it starts.

2.DALVIK.VM.HEAPGROWTHLIMIT=64M (maximum memory per application can be allocated to 64m)
Over it will crash and quit the app ... I guess that's right.

3.dalvik.vm.heapsize=256m (maximum memory allocated to single virtual machine 256m)

The amount of memory allocated here affects the entire system's use of RAM, and the rate at which the program reacts after running for a period of time.

The larger the value, the faster the system consumes RAM, but the program runs very stably, especially when the content loading speed of the game and video program can be greatly improved.

The smaller the value, the more RAM is left on the system, but the program will be very loading, especially if the game will take a lot of time to switch scenes.

If an application needs to use memory that exceeds this value, the system's garbage collector will be triggered and the system and program will be jammed.

With the above set.
Every time you open an app, the system will draw 8m of dynamic memory for the program to use, more than the part will be +8m
A total of 7 times 8m, including a first set of 8m, a total of 64m, this is a single program's maximum dynamic memory usage
More than that, the program will crash (automatically end off)
The maximum amount of memory 256m a single virtual machine can allocate, meaning a program that can fill 64m memory X4
More than part of the virtual machine will be forced to reclaim the memory of the program, on the one hand, forced to shut down some programs, on the one hand to load the program to partition new memory, this time will appear in Carrington

Because everyone uses different habits, sometimes love to install a bunch of widgets (gadgets) on the desktop, only on the desktop is not often used, perhaps a single widget as long as 3-5m, if today at the beginning of the division of 8m memory to him, for a resident less than 5M program, will waste 3M of memory, General Original ROM Idle program + background program on about 30, each waste about 3 m memory. It's almost a waste of 90M.
So we can put
1.dalvik.vm.heapstartsize=8m, change to =4m, then reboot.
When you're on standby, you'll find that there's less memory in use and more memory available, even though you're using desktop gadgets
may not be better than the original, because the system is still helping the program to divide the new memory space, but also not the Dayton

2.dalvik.vm.heapgrowthlimit=64m do not have to change, now the app in the foreground eat a lot of memory
If you change the small to 32m, it assumes that the program memory to eat to 40m will be enough, the program may be to you to see

3..dalvik.vm.heapsize=256m (a single virtual machine can allocate the maximum memory 256m), although it is to write a single virtual machine, but the system will actually produce how many virtual machines ... I'm not sure, but the only certainty is that no more than the actual amount of RAM available
Remember S3 is 1G RAM, but actually it looks like 780M (the other seems to be the GPU)
780/256=3 ..., about 3 virtual machines (this should be the case)
People who want to see more RAM can change the 256 to 128m, reboot ... You will find that the available memory has become more ...
But again, when you start a new program, you want to divide the new virtual machine +128, it may be slower, but it will save memory without wasting

The above is sacrificing some open speed, but can slow down the system forced to reclaim memory Duncuo sense
---------------------------------------------------------------------------

Lazy Person Summary S3 version
1. Want to install a lot of widget gadgets to the desktop, recommend
Dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=40m
dalvik.vm.heapsize=160m
Maybe the program is not so fast, but not cotton, and the available memory will be more
--------------
2. As long as playing games, the desktop is very clean and boring, do not install other widget gadgets
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=384m
Load a large program or game faster, the disadvantage is that the available memory is smaller

-----------------------------------------
S3 LTE (I9305) default Dalvik is the same as S3
But it can be changed (I also set it)
Dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
Dalvik.vm.heapsize=576m (1750/576=3 ...) 3 virtual machines can be made.
(576/8) programs under 8M can have 72 idle programs
(576/64) A virtual machine can accommodate more than 9 workers