LocalLLaMA post links KV-approximation prefill demo, asks whether 27B Qwen can match

A post on r/LocalLLaMA links to a browser demo that its submitter says reproduces, in a limited way, the KV-cache trick behind V4.1 flash's fast prefill, and shows it working on Qwen. The thread was submitted by the Reddit account u/T_rex2700, and its title states that someone "apparently" managed to "kind of replicate" the behaviour. The only artifact attached is a URL, https://kishida.github.io/webdemos/llkvapprox/. No code repository or write-up accompanies it.

Those two hedges carry the post's claim load. "Apparently" marks the result as second-hand, and "kind of" limits it to a partial match rather than a full reproduction. The post never names the organisation that ships V4.1 flash, and it does not say which Qwen checkpoint the demo runs on. What it does name is the target of the comparison: the flash model's handling of KV during prefill, applied to a Qwen model.

Fast prefill is the property the post is chasing. A model reads the whole prompt in one pass and writes keys and values for those tokens into a cache that generation reads back afterwards, and a long prompt makes that pass the first visible latency before any output appears. The post treats that step as something V4.1 flash handles well and open Qwen models do not, which is what the demo's URL name, llkvapprox, appears to abbreviate. What the approximation costs in output quality goes unstated.

The post supplies no measurements. There is no tokens-per-second figure, no comparison against an unmodified Qwen baseline, no hardware listed, and no indication of how much approximation error the method introduces. A demo page is the entire evidence base so far.

The body of the post turns the result into a question about scale. "I wonder someone will figure out a way to do this with 27B?" it reads, which puts the current demo below that size and leaves open whether the approach extends to it. The same line directs readers to throw Qwen3 at the page, naming the model family for anyone who wants to run the test instead of taking the claim on trust.

No other coverage of the demo accompanied the submission, and it carries no comment from Qwen's maintainers or from whoever develops V4.1 flash. The item therefore rests on one anonymous Reddit post and the page it links to, with the replication claim unverified by any third party. The poster does not say whether code, weights, or a technical write-up will follow.

The next test is whether the demo holds up when other people load it with their own models and prompts, which is the check the post itself proposes. Whether the 27B case is a matter of scale or a different problem entirely remains open, and on that question the post offers nothing yet.