diff options
| author | Christopher Tate <ctate@google.com> | 2018-01-31 13:24:14 -0800 |
|---|---|---|
| committer | Chris Tate <ctate@android.com> | 2018-02-15 18:26:56 +0000 |
| commit | d1aebb35a8b6466435f64fcb470c6893c1c1de8c (patch) | |
| tree | bc55823da2081b09eb62e7ff4688f5284865c6e7 /rs/java/android/renderscript/ProgramVertexFixedFunction.java | |
| parent | 2d375453ec8ed8a2957afb7ea493625e48e362e2 (diff) | |
Correct job base heartbeat calculation
The "how many buckets ago did we last run" calculation was wrong, in a
way that was too aggressive about throttling execution. We no longer
use a per-job base runnability milestone; instead, the app as a whole
experiences runnability intervals every so often based on its standby
state.
We also now specifically allow for newly-scheduled jobs within the app's
standby-defined execution slot to run within that slot, rather than
having to wait for the next one.
A small stats bug has been fixed in the job-start code: we would
previously log a job start event in battery stats even when the intended
job turned out to be unlaunchable.
Finally, there's a new 'heartbeat' shell command that allows a tester
to read or advance the standby heartbeat.
Change-Id: Icf03f82e2fde7408095f6d06642d944c3ae10a26
Fixes: 72713333
Test: atest CtsJobSchedulerTestCases
Diffstat (limited to 'rs/java/android/renderscript/ProgramVertexFixedFunction.java')
0 files changed, 0 insertions, 0 deletions