Revert "CameraMetadata: Add trace points CameraMetadata operations"
This reverts commit 47cdcf39. Reason for revert: Each ATRACE_CALL operation has around 10us of perf cost. For cases like 240fps recording, each removeInFlightMapEntry operation, on an average has 20-30 CameraMetadata constructions, costing us .2 - .3ms in latency. This is around 6% of the ~4ms budget that we have. According to https://source.android.com/setup/develop/new-device#build-variants 'Any debugging features that are enabled by default in userdebug should be clearly defined and shared with all developers working on the project. You should enable debugging features only on a limited-time basis until the issue you're trying to debug is resolved'. Reverting this change now that http://b/144028609 has been resolved. Bug: 155910869 Test: builds Signed-off-by:Jayant Chowdhary <jchowdhary@google.com> Change-Id: I56e471a83097527a1a211c61c3bd73136a82b6b6
Loading
Please register or sign in to comment