Marc-André Bombeck 76e621b067 perf(tz): memoise zone offsets per hour for wall-clock reads ...

Day keys and wall-clock fields are computed per row in the analytics,
digest and personal-record loops, and each call ran
Intl.DateTimeFormat#formatToParts plus a resolvedOptions() allocation
to re-validate the zone. In a CPU profile of an Insights page load the
zone helpers were 17-19% of the busy time on the request thread.

Probe the offset once per UTC hour at both ends of the hour and derive
the wall clock arithmetically; an hour that contains a transition, an
instant outside 1971-2199 or an invalid date keeps the formatter path.
Zone validity is memoised per name. userDayKey drops from 9.3 to 1.5 us
per call, wallClockInTz from 6.4 to 0.5 us; a parity test checks the
result against Intl around every 2026 transition in ten zones.

2026-10-04 15:53:48 +02:00

..

__tests__

perf(tz): memoise zone offsets per hour for wall-clock reads

2026-10-04 15:53:48 +02:00

date-only.ts

fix(dates): read date-only lab and document dates as calendar dates

2026-10-01 22:14:07 +02:00

format.ts

perf(tz): memoise zone offsets per hour for wall-clock reads

2026-10-04 15:53:48 +02:00

intl-cache.ts

fix(api,lib): consent before reuse, tighter inputs and caches that tell on themselves

2026-06-11 23:20:38 +02:00

local-day.ts

fix(tz): one start-of-day for every zone, including skipped midnights

2026-09-26 15:41:16 +02:00

resolver.ts

fix(tz): one default zone, and the user's own calendar where Berlin was hard-coded

2026-09-26 16:23:14 +02:00

start-of-utc-day.ts

fix(mood): key mood rollups by the local day, not the UTC day

2026-07-24 03:50:14 +02:00

wall-clock.ts

perf(tz): memoise zone offsets per hour for wall-clock reads

2026-10-04 15:53:48 +02:00

zone-offset.ts

perf(tz): memoise zone offsets per hour for wall-clock reads

2026-10-04 15:53:48 +02:00