1 files changed, 13 insertions(+), 17 deletions(-)

M PLAN.md

@@ 194,25 194,21 @@ fiber and bridges client ↔ handler via `fiber.channel`. All four flavors
       `:encode` all compile with no fatal aborts.
 
       Workload characteristics (from `tarantool bench/lazy_bench.lua`,
-      Person at 1KB / 10KB / 100KB):
-       - **Passthrough re-encode** is the headline win: **1.0–1.5×**
+      Person at 1KB / 10KB / 100KB, after the SoA index refactor):
+       - **Passthrough re-encode** is the headline win: **1.6–1.9×**
          faster than eager decode→encode across all sizes and both modes.
          Untouched views never re-walk the wire.
-       - **Sparse read** (`:get` two top-level fields) is **0.60–0.77×
-         of eager** on the emails-heavy Person shape. Index-build
-         allocates one segment table per wire entry, and for messages
-         that scale via repeated leaves (no deeply-nested subtrees that
-         `skip_field` can vault over), that allocation cost cancels the
-         decode-skip savings. Lazy still wins this shape on payloads
-         dominated by nested submessages — that case isn't represented
-         in the current bench.
-       - **Mutate-then-reencode** is **0.81–1.07× of eager**; ~break-even
-         to slight loss on the same flat shape. Both decode+set+encode
-         and decode_lazy+set+encode walk the full byte range; lazy
-         splices substrings, eager re-emits per-field.
-      The honest framing: lazy is a *byte-passthrough* optimization;
-      it's not a universal speedup. Use it when you decode, touch few
-      fields, and re-encode — the common proxy/router shape.
+       - **Sparse read** (`:get` two top-level fields) is **0.90–1.16×
+         of eager**: break-even at small sizes, slight win at 100KB
+         (especially in runtime mode where eager pays more dispatch
+         cost). Earlier 0.60–0.77× regression came from one Lua table
+         per wire entry; replacing with parallel int arrays closed the
+         allocation gap.
+       - **Mutate-then-reencode** is **1.09–1.26× of eager**; the
+         per-field splice path now consistently beats full re-encode.
+      The honest framing: lazy is a *byte-passthrough* optimization
+      that also handles sparse reads at parity. Best fit: proxy /
+      router shapes that decode, touch a few fields, and re-encode.
 
 ### M7 — Developer ergonomics