diff options
| author | 2021-06-25 22:26:45 +0000 | |
|---|---|---|
| committer | 2021-06-25 22:26:45 +0000 | |
| commit | 54996e2d0e16f90c8a0ea4c3cbdf4e40fe560646 (patch) | |
| tree | 26677ee3bbafdbba717307c17f8f82a74255f879 /services/surfaceflinger/FrameTimeline | |
| parent | 757f24e3872d42283404dcf1c0fe88a4d8dd7ac8 (diff) | |
Make deadlineThreshold 0
We give 2ms threshold for the deadline and this seems to cause some
misclassifications where an app's fault was classified as SF scheduling.
We designed the threshold with the idea of tweaking, so try 0 threshold
and see if it works better.
Bug: 191238086
Test: libsurfaceflinger_unittest
Change-Id: I0ac3d9ce3f9ec90f6b3188009d9d09a69afd37b2
Diffstat (limited to 'services/surfaceflinger/FrameTimeline')
| -rw-r--r-- | services/surfaceflinger/FrameTimeline/FrameTimeline.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/services/surfaceflinger/FrameTimeline/FrameTimeline.h b/services/surfaceflinger/FrameTimeline/FrameTimeline.h index 15ecf130e7..139f91f3bc 100644 --- a/services/surfaceflinger/FrameTimeline/FrameTimeline.h +++ b/services/surfaceflinger/FrameTimeline/FrameTimeline.h @@ -96,7 +96,7 @@ struct JankClassificationThresholds { // The various thresholds for App and SF. If the actual timestamp falls within the threshold // compared to prediction, we treat it as on time. nsecs_t presentThreshold = std::chrono::duration_cast<std::chrono::nanoseconds>(2ms).count(); - nsecs_t deadlineThreshold = std::chrono::duration_cast<std::chrono::nanoseconds>(2ms).count(); + nsecs_t deadlineThreshold = std::chrono::duration_cast<std::chrono::nanoseconds>(0ms).count(); nsecs_t startThreshold = std::chrono::duration_cast<std::chrono::nanoseconds>(2ms).count(); }; |