Proposal to set dalvik-vm optimizing all code
I played with the dalvik.vm.dexopt-flags in /system/build.prop. Basically you control the class-loading and dalvik-vm there.
streakowner proposed in http://forum.xda-developers.com/show...&postcount=644
the setting v=n,o=v. But disabled this with #, in DSC v1.0 the setting is active.
That means: do not verify and optimize mode verified. Found that info in dexopt/OptMain.c
I did some performance measurement with smartbench 2011 and got the value 553
in the first round, and 465
in the second round. That is very bad for an one ghz powered device. Good would > 1000. /data/dalvik-cache takes 74 MiB with this setting.
At the moment I'm running with
That means: do not verify, optimize all classes and optimize for uniprocessor.
First I was not impressed, because rebooting with a cleaned dalvik-cache
took more than double the time span of the o=v setting. logcat is full off lines telling me what can't be optimized and how much time the load took. But after booting I got the impression the system went faster. With smartbench 2011 I get the value 1036
in the first and 1110
in the second round. /data/dalvik-cache takes 74 MiB with this setting.
Can someone confirm my finding?
I don't say you will double the speed of the streak with this setting. But I think you will notice the change. The trade off is the time for the first boot. But I think that is worth is.
So I propose to use the above setting in all gb-based roms for the streak 5.
Have a nice weekend,