flounder: limit dex2oat to one threadandroid-7.1.2_r9android-7.1.2_r8android-7.1.2_r6android-7.1.2_r5android-7.1.2_r4android-7.1.2_r39android-7.1.2_r38android-7.1.2_r37android-7.1.2_r36android-7.1.2_r33android-7.1.2_r32android-7.1.2_r30android-7.1.2_r3android-7.1.2_r29android-7.1.2_r28android-7.1.2_r27android-7.1.2_r25android-7.1.2_r24android-7.1.2_r23android-7.1.2_r2android-7.1.2_r19android-7.1.2_r18android-7.1.2_r17android-7.1.2_r16android-7.1.2_r15android-7.1.2_r14android-7.1.2_r13android-7.1.2_r12android-7.1.2_r11android-7.1.2_r10android-7.1.2_r1nougat-mr2.3-releasenougat-mr2.2-releasenougat-mr2.1-releasenougat-mr2-security-releasenougat-mr2-releasenougat-mr2-pixel-release

Denver processor only has 2 cpus, we should limit dex2oat
background operations to 1 thread and the associated lower
memory footprint so that the impact is controlled.

Bug: 34114061
Test: manual smoke test
Change-Id: I1f32b1734aad5765223959a9735a66b086e3448a

1 files changed, 3 insertions, 0 deletions

diff --git a/device.mk b/device.mk
index 6a40714..0735702 100644
--- a/device.mk
+++ b/device.mk
@@ -226,6 +226,9 @@ PRODUCT_PROPERTY_OVERRIDES := \
 
 # setup dalvik vm configs.
 $(call inherit-product, frameworks/native/build/tablet-10in-xhdpi-2048-dalvik-heap.mk)
+# N9 has only two CPUs, so drop dex2oat pressure after boot at runtime
+PRODUCT_PROPERTY_OVERRIDES += \
+    dalvik.vm.dex2oat-threads=1
 
 # for off charging mode
 PRODUCT_PACKAGES += \