)]}'
{
  "commit": "fd2b786912b72f53f52a39880a4c1cad74ff2841",
  "tree": "c8d0b8d062224a02a07307fcd941bd1ddd529052",
  "parents": [
    "8a19587f2832b1c852d2a8740e5a2b85a6a2fd68"
  ],
  "author": {
    "name": "Matt Buckley",
    "email": "mattbuckley@google.com",
    "time": "Tue Dec 03 17:18:33 2024 -0800"
  },
  "committer": {
    "name": "Matt Buckley",
    "email": "mattbuckley@google.com",
    "time": "Wed Dec 04 12:07:46 2024 -0800"
  },
  "message": "Add CPU/GPU_LOAD_SPIKE hints for one-off expensive workloads\n\nCurrently there is ambiguity between single-frame expensive ops\n(eg: shader compilation) and longer-duration expensive ops (eg:\nSF client compositon). This load hint aims to resolve this by\nexplicitly annotating one-time expensive workloads so they can\nbe given unique boost and hysteresis expectations.\n\nFor example, a load_spike aware tracker might want to ignore\nthe timing that comes from a LOAD_SPIKE-marked frame, as it is\nknown to not be representative of the overall workload.\n\nFlag: EXEMPT NDK\nTest: atest PerformanceHintNativeTestCases\nTest: atest PerformanceHintManagerTest\nBug: 367803904\nChange-Id: I22458f0d8f0819499f3463aa36e8bb7eb7af15be\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ca86c2730ff488d5881738154bd9519dfa4f0fbf",
      "old_mode": 33188,
      "old_path": "include/android/performance_hint.h",
      "new_id": "2b4a5f5f53c9c3de3c371d819d2fda77f77def91",
      "new_mode": 33188,
      "new_path": "include/android/performance_hint.h"
    },
    {
      "type": "modify",
      "old_id": "f150fb1f3e7b5d986a95d73447af5393620bd82e",
      "old_mode": 33188,
      "old_path": "include/private/performance_hint_private.h",
      "new_id": "e3f98badbea664363b3d2190cf951ee4ec191555",
      "new_mode": 33188,
      "new_path": "include/private/performance_hint_private.h"
    }
  ]
}