Use duration not threadDuration for frame duration (#13117)
1. We want to measure wall-clock duration for the benchmarks, as opposed to thread duration (e.g., waiting on a mutex should accrue time) and 'dur' is the metric to use for that. 2. On Darwin-based systems (macOS and iOS) 'tdur' is the result of a mach syscall lookup to thread_info. This call returns unreliable data on iOS. Chromium, for example, disables thread time support entirely for iOS.
Showing
Please register or sign in to comment