From 725211d51bf16244fa8b73693f8b73818095d3db Mon Sep 17 00:00:00 2001 From: tannevaled Date: Sat, 14 Nov 2026 22:43:18 +0100 Subject: [PATCH] README: Workspace figures compare Go with Go; NumPy ratios were multicore (#118) Co-Authored-By: Claude Opus 5.5 --- README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 42d3f4c..3286c1a 100644 --- a/README.md +++ b/README.md @@ -100,8 +100,11 @@ for step := 0; step < steps; step++ { After the first pass nothing is allocated, nothing is zeroed that the kernel overwrites anyway, and the memory stays warm in cache: `x + y` on 1 024 -elements goes from 2.6 µs to 0.38 µs (2.1× NumPy), `sqrt(x*y + x)` on 256 Ki -from 1.18 ms to 0.39 ms (7.5× NumPy). ⚠ An array allocated from the workspace +elements goes from 2.6 µs to 0.38 µs, and `sqrt(x*y + x)` on 256 Ki from +1.18 ms to 0.39 ms. Those two figures compare Go with Go. The NumPy figures once +quoted beside them came from multicore runs. On one core, the allocating +forms are about 3× slower than NumPy, while the preallocated `*Into` forms tie +with it ([docs/perf.md](docs/perf.md), #118). ⚠ An array allocated from the workspace is invalid after `Reset`; `Detach` is how a result leaves it. The `*Into` methods (`AddInto`, `SqrtInto`, …) remain the way to reuse one named buffer.