#clockgettimensecnp — Public Fediverse posts

Swift’s native Clocks are very inefficient

By which I mean, things like ContinuousClock and SuspendingClock.

In absolute terms they don't have much overhead - think sub-microsecond for most uses. Which makes them perfectly acceptable when they're used sporadically (e.g. only a few times per second).

However, if you need to deal with time and timing more frequently, their inefficiency can become a serious bottleneck.

I stumbled into this because of a fairly common and otherwise uninteresting pattern - throttling UI updates on an [...]

https://wadetregaskis.com/swifts-native-clocks-are-very-inefficient/

Swift’s native Clocks are very inefficient

By which I mean, things like ContinuousClock and SuspendingClock.

In absolute terms they don't have much overhead - think sub-microsecond for most uses. Which makes them perfectly acceptable when they're used sporadically (e.g. only a few times per second).

However, if you need to deal with time and timing more frequently, their inefficiency can become a serious bottleneck.

I stumbled into this because of a fairly common and otherwise uninteresting pattern - throttling UI updates on an [...]

https://wadetregaskis.com/swifts-native-clocks-are-very-inefficient/

Swift’s native Clocks are very inefficient

By which I mean, things like ContinuousClock and SuspendingClock.

In absolute terms they don't have much overhead - think sub-microsecond for most uses. Which makes them perfectly acceptable when they're used sporadically (e.g. only a few times per second).

However, if you need to deal with time and timing more frequently, their inefficiency can become a serious bottleneck.

I stumbled into this because of a fairly common and otherwise uninteresting pattern - throttling UI updates on an [...]

https://wadetregaskis.com/swifts-native-clocks-are-very-inefficient/