)]}'
{
  "commit": "2e310dade1053e6ced4c419e073badf6a12eec03",
  "tree": "00239ff3b329ee5707450d1ada866254e9e16a17",
  "parents": [
    "5120edaad25acb60218d81bde9a1e7b79ac3f143"
  ],
  "author": {
    "name": "Jayant Chowdhary",
    "email": "jchowdhary@google.com",
    "time": "Tue May 12 12:40:36 2020 -0700"
  },
  "committer": {
    "name": "Jayant Chowdhary",
    "email": "jchowdhary@google.com",
    "time": "Tue May 12 12:49:58 2020 -0700"
  },
  "message": "Revert \"CameraMetadata: Add trace points CameraMetadata operations\"\n\nThis reverts commit 47cdcf399ff933d2bec4e505a02938311c9f5e32.\n\nReason for revert: Each ATRACE_CALL operation has around 10us of perf cost. For cases\nlike 240fps recording, each removeInFlightMapEntry operation, on an\naverage has 20-30 CameraMetadata constructions, costing us .2 - .3ms in\nlatency. This is around 6% of the ~4ms budget that we have.\n\nAccording to\nhttps://source.android.com/setup/develop/new-device#build-variants\n\n\u0027Any debugging features that are enabled by default in userdebug should\nbe clearly defined and shared with all developers working on the\nproject. You should enable debugging features only on a limited-time\nbasis until the issue you\u0027re trying to debug is resolved\u0027.\n\nReverting this change now that http://b/144028609 has been resolved.\n\nBug: 155910869\n\nTest: builds\nSigned-off-by: Jayant Chowdhary \u003cjchowdhary@google.com\u003e\nChange-Id: I56e471a83097527a1a211c61c3bd73136a82b6b6\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4745ee8ab9ad1f4750530e38d45a6998ac1b214e",
      "old_mode": 33188,
      "old_path": "camera/CameraMetadata.cpp",
      "new_id": "135384adb1202e00975b1374c5c7106677f13b6a",
      "new_mode": 33188,
      "new_path": "camera/CameraMetadata.cpp"
    }
  ]
}
