Eliminate lambdas from tracing helper macro
In the change with ID Ibee1e7dc5021296bdb5871dec59d8d4978fcf0c9, we introduced lambdas at the tracing sites so that we could conditionally execute the code to generate the tracing string only when tracing was enabled. However, it seems like the introduction of the lambdas, especially ones that capture everything by reference, have added a performance burden, causing ~5% increase in latency in the input pipeline. In this CL, we remove the lambdas from the tracing sites, and instead rely on the expression evaluation guarantees of the ternary to ensure that the expression to generate the trace message will only be evaluated when the condition is true. Bug: 297462790 Test: Will evaluate perf metric after submitting Change-Id: I69b37551c4b23256c64544e0ddf4b5b39a9403fb
Loading
Please register or sign in to comment