Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Mo 17.06.2024 00:04:17 73.470 0 2.322.273 31,6 Mastodon 4.2.8 500 So 16.06.2024 00:04:20 73.470 0 2.320.277 31,6 Mastodon 4.2.8 500 Sa 15.06.2024 00:01:16 73.470 -1 2.318.273 31,6 Mastodon 4.2.8 500 Fr 14.06.2024 00:00:23 73.471 -2 2.316.028 31,5 Mastodon 4.2.8 500 Do 13.06.2024 00:00:38 73.473 -2 2.315.785 31,5 Mastodon 4.2.8 500 Mi 12.06.2024 00:00:06 73.475 -1 2.313.166 31,5 Mastodon 4.2.8 500 Di 11.06.2024 00:14:13 73.476 -1 2.310.989 31,5 Mastodon 4.2.8 500 Mo 10.06.2024 00:01:00 73.477 -1 2.308.814 31,4 Mastodon 4.2.8 500 So 09.06.2024 00:15:11 73.478 0 2.306.672 31,4 Mastodon 4.2.8 500 Sa 08.06.2024 00:05:14 73.478 0 2.304.616 31,4 Mastodon 4.2.8 500
Litherum (@litherum) · 11/2022 · Tröts: 2.337 · Folger: 400
Mo 17.06.2024 06:40
Speaking of Apple's crazy system, after MTLCommandBuffers finish running, the GPUStartTime and GPUEndTime fields report "The host time, in seconds, when the GPU starts command buffer execution." https://developer.apple.com/documentation/metal/mtlcommandbuffer/1639924-gpustarttime
So, if they're measuring events that happen on the GPU, but reporting the host time, that means Metal is already able to correlate GPU time to CPU time internally. So why do they force applications to continually cross-reference the clocks themselves?
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0 · via Web