> we’re talking a mere 19 to 30 nanoseconds to get the time elapsed since a refe... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		foolswisdom on May 6, 2024 \| parent \| context \| favorite \| on: Swift's native Clocks are inefficient > we’re talking a mere 19 to 30 nanoseconds to get the time elapsed since a reference date and compare it to a threshold. The table shows 19 or 30 milliseconds for Date / NSDate. Or am I misunderstanding something?

taspeotis on May 6, 2024 | [–]

Divide by a million

Medea on May 6, 2024 | [–]

"showing the median runtime of the benchmark, which is a million iterations of checking the time"

foolswisdom on May 6, 2024 | [–]

Thanks.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact