tree 2b8dea1d41af38da4041353dc3e76a891e5c343e
parent a95b752dc6ee807e74bc3efd1b8985e69a2d7152
author Chris Bracken <chris@bracken.jp> 1511228234 -0800
committer GitHub <noreply@github.com> 1511228234 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJaE4NKCRBK7hj4Ov3rIwAAdHIIAD4drSDP0vBFBsGspW2BX/NK
 Zcia/64/xFSxA7rvENUxNC8+EYCXUXEECjCRiwKcprk8qNNmVRiyXsMPckDQH50z
 BPuWYAnsQne1WC8YNyxF31esuMk4LiZbDewUPPAZRPPStj3q2BveUtC3N6YQKJ64
 ooIG5BoCOxY7PRUuxMMQQ0hbotcNRIV1hf0GKcBpGfKr5Z18KGmrowEyBy9lwslq
 ub7Cd/9tCE0U3TpxP2EXrSWjeDECeRpO57AdQ0YIWkDrMByKl/YUrxwCvGoTLPo7
 jtlYVgiuLzdCxHxRFVg0O1z7F6vbc715uWaoe7MFx35b5crPPBzh6RnNdmEVvkI=
 =YgaH
 -----END PGP SIGNATURE-----
 

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.