aboutsummaryrefslogtreecommitdiff
path: root/.claude
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-12 00:09:15 -0500
committerCraig Jennings <c@cjennings.net>2026-05-12 00:09:15 -0500
commit94ee5e4fac213de915a27906e4e0861e86de8914 (patch)
tree9f8ee61efaefa9fedc1c79d7ff9a432cf0d3b96d /.claude
parent2b88c6a83f854c3e166774d2855491de6e230d03 (diff)
downloaddotemacs-94ee5e4fac213de915a27906e4e0861e86de8914.tar.gz
dotemacs-94ee5e4fac213de915a27906e4e0861e86de8914.zip
test(lorem-optimum): tag benchmarks :perf and assert on scaling ratios
The benchmark suite carried no tag, so `make test' ran it every time, and three of its tests asserted absolute wall-clock times (`(should (< time 5000.0))' and friends). Those numbers hold on my laptop and break on a slower box. Every benchmark is now `:perf'-tagged so the default test run skips it. The three absolute learn thresholds collapse into one `benchmark-learn-scaling' test: it times 1K, 10K, and 100K learns and requires each 10x jump in input to cost under 40x the time. Linear scaling lands near 10x, and the 40x ceiling tolerates GC pauses and slow hardware while still catching an O(N^2) regression. The rest drop their absolute `should's and stay as timing reports for `make benchmark'.
Diffstat (limited to '.claude')
0 files changed, 0 insertions, 0 deletions