Proposal to set dalvik-vm optimizing all code

---

Hello,

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

dalvik.vm.dexopt-flags=v=n,o=a,u=y

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,
hunderteins

Tested on miui and it's not working i get into a boot loop.

getprop | grep dexopt
[dalvik.vm.dexopt-flags]: [v=n,o=a,u=y]

Well, same ~950 in Quadrant (CPU/mem only)

998400

--
Sergei.

Originally Posted by _2bad4u_

Tested on miui and it's not working i get into a boot loop.

Ouch! Sorry to hear that. I hope you didn't get in serious trouble.

Originally Posted by _n0p_

getprop | grep dexopt
[dalvik.vm.dexopt-flags]: [v=n,o=a,u=y]

Well, same ~950 in Quadrant (CPU/mem only)

998400

Quadrant shows 1048 with o=a and 1065 with o=v. Thats not helping either. At least smartbench shows nearly the same "Games Index". But what do they test with ther productivity index? Calculating PI and mandelbrot is so different?
And there is opera. Its definitly faster with o=a. I'll try to find a web page rendering test.

o.k. I get more mixed signals here. Numion tells me that rendering a real world web-page is about 30% faster with o=a (10.5 vs. 14,6 sec). Scragz is 10 % slower with o=a ( 9.7 vs. 10.5 sec).

I'll file it under works for me, but don't try this with miui. Thanks for your help.

Reg. hunderteins

No problem happy to help

hunderteins, this actually lead me to think that you'll try to build highly optimized (armv7, neon, no loop unroll - small cache) libdvm. Am I right?

Originally Posted by _2bad4u_

Tested on miui and it's not working i get into a boot loop.

It works with MIUI too but you have to delete the another line that contains

dalvik.vm.dexopt-flags=m=y

i guess this lines value is overlapping with the other lines "u=y" value.

---------- Post added at 08:11 AM ---------- Previous post was at 08:03 AM ----------

The result of first test is:
Productivity index=716
Gaming index=981

with smart bench 2012

---------- Post added at 08:20 AM ---------- Previous post was at 08:11 AM ----------

The result of second test is:

Productivity index=1074
Gaming index=1569

with smart bench 2011

DS 5 works faster than ever!

Thank you!

Originally Posted by hunderteins

Hello,

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

dalvik.vm.dexopt-flags=v=n,o=a,u=y

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,
hunderteins

Sent from my Dell Streak using Tapatalk 2

Testing this now. Opera Mobile is definitely faster, and I honestly think the start time from a wipe of the dalvik cache wasn't any longer than normal.