The VMCompilationPerformance profile is used to run Isolated Compilation
in a Protected VM, normally during the device idle, where relevant
APEXes are staged.
The original VMCompilationPerformance introduced in aosp/2060891 does
not have any specific definition and requires vendors to customize it.
This change re-defines it as an aggregated profile with a default set of
existing profiles, so that performance can be reasonable by default.
This profile may be renamed to a more generic name later, e.g.
"SCHED_SP_COMPUTE".
Bug: 231437770
Test: Run `composd_cmd test-compile` on a local device.
Before: 1m50s +/- 10s (with whatever that's default)
After: 1m25s +/- 5s
Ignore-AOSP-First: cherry pick from aosp/2097065
Change-Id: Ib8cd65782c818474fb129efbd9ef9a3e23ad1eb3
Merged-In: Ib8cd65782c818474fb129efbd9ef9a3e23ad1eb3
|
||
|---|---|---|
| .. | ||
| Android.bp | ||
| cgroups.json | ||
| cgroups.proto | ||
| cgroups.recovery.json | ||
| cgroups_28.json | ||
| cgroups_29.json | ||
| cgroups_30.json | ||
| cgroups_test.h | ||
| task_profiles.json | ||
| task_profiles.proto | ||
| task_profiles_28.json | ||
| task_profiles_29.json | ||
| task_profiles_30.json | ||
| task_profiles_test.h | ||
| test.cpp | ||
| test_vendor.cpp | ||