Add corpus loading and year-range caching #96

New issue

Closed

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

manlycucumber commented

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

(Migrated from github.com)

Problem

Generating a full year or repeated lookups should not reload and recompute the corpus each time. Caching of loaded corpus and computed temporal skeletons is needed.

Acceptance criteria

Corpus is loaded once per process and reused
Per-year temporal skeletons are cached
A year-range benchmark shows the expected speedup
Cache correctness is asserted against uncached output

Notes

Cache must be invalidated by the data-version stamp.

## Problem Generating a full year or repeated lookups should not reload and recompute the corpus each time. Caching of loaded corpus and computed temporal skeletons is needed. ## Acceptance criteria - [ ] Corpus is loaded once per process and reused - [ ] Per-year temporal skeletons are cached - [ ] A year-range benchmark shows the expected speedup - [ ] Cache correctness is asserted against uncached output ## Notes Cache must be invalidated by the data-version stamp.

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#96

No description provided.

Rows
Columns