Benchmark and optimise single-day resolution #95

New issue

Closed

opened 2026-07-01 00:53:48 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 00:53:48 +00:00

(Migrated from github.com)

Problem

The API will call day() at high volume. Resolution must be benchmarked and any hot paths (Computus, overlay application, precedence walk) optimised to a budget.

Acceptance criteria

A benchmark measures single-day resolution time
A documented budget is met for a cold and warm call
Hot paths identified and optimised without changing output
Validation suite still passes post-optimisation

Notes

No behaviour change; output must remain byte-stable.

## Problem The API will call day() at high volume. Resolution must be benchmarked and any hot paths (Computus, overlay application, precedence walk) optimised to a budget. ## Acceptance criteria - [ ] A benchmark measures single-day resolution time - [ ] A documented budget is met for a cold and warm call - [ ] Hot paths identified and optimised without changing output - [ ] Validation suite still passes post-optimisation ## Notes No behaviour change; output must remain byte-stable.

manlycucumber referenced this issue from a commit

2026-07-12 18:46:22 +00:00

perf: resolution benchmark, cache-flush hook, and budget (#95, #96) (#474)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Directorium/Core#95

No description provided.

Rows
Columns