Those macros are performance-tracking counters used in microbenchmarks. We count our use of atomic operations, locks, and mallocs since these are all (relatively) expensive operations and often foreshadow performance regressions (or improvements). The results of these can be seen on the Checks section of any PR on our Github repo (though they are only shown if there's a significant change).
On Tuesday, October 29, 2019 at 10:07:42 AM UTC-7, Saroj Mahapatra wrote: > > Hi, > > Why does comoare_exchange_week call gpr_atm_inc_cas_then before calling > the std function? > > Thank you. > > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/f73544d2-0c5b-45be-914b-0945f8ba1a98%40googlegroups.com.
