Kimi Delta Attention versus Transformer [ftip-00K2]
✍️sourceAGENTDRAFTED
Kimi Delta Attention versus Transformer [ftip-00K2]
✍️sourceAGENTDRAFTED
Definition 1. KDA model-instance record [ftip-00K3]AGENTDRAFTED
Definition 1. KDA model-instance record [ftip-00K3]AGENTDRAFTED
For a Kimi Delta Attention (KDA) versus full-attention baseline study, record the exact Kimi Linear checkpoint, layer mix, context length, hardware, kernel, precision, batch, and decoding workload. The paper describes KDA as a fine-grained gated delta-rule module in a hybrid architecture; those are source observations from Kimi Linear: An Expressive, Efficient Attention Architecture[kimi2025linear], not universal theorems.
If the baseline is called a Transformer, record whether it is the paper's MLA baseline or another full-attention implementation; the label alone does not identify a common architecture or cost.
Example 2. Matched-cost KDA and Transformer comparison [ftip-00K4]AGENTDRAFTED
Example 2. Matched-cost KDA and Transformer comparison [ftip-00K4]AGENTDRAFTED
A matched comparison uses the same task prompts, post-training data and feedback, optimizer family, evaluation protocol, and quality target. The corresponding measurements include parameter count, training FLOPs, inference FLOPs, wall time, memory, KV-cache bytes, and context length for each architecture. A reported speed or quality difference is conditional on these experimental conditions and measurements.
Remark 3. What the Kimi Linear paper establishes [ftip-00K5]AGENTDRAFTED
Remark 3. What the Kimi Linear paper establishes [ftip-00K5]AGENTDRAFTED
Kimi Linear reports a hybrid KDA/MLA model and fair-comparison experiments in Sections 3--5, with setup in Section 5.4 and efficiency comparisons in Sections 5.5--5.6 of Kimi Linear: An Expressive, Efficient Attention Architecture[kimi2025linear]. These include long-context efficiency.
The reported throughput and quality are empirical under its training recipe and hardware; they are lower bounds on demonstrated performance, not an architecture-independent ceiling.
Example 4. Parameter matching is not cost matching [ftip-00K6]AGENTDRAFTED
Example 4. Parameter matching is not cost matching [ftip-00K6]AGENTDRAFTED
Two models with equal parameter count can have different attention FLOPs, KV-cache memory, kernel utilization, and attainable context. Conversely, equal wall time can hide different hardware and precision. Therefore a parameter-matched result cannot by itself identify a compute frontier.
Remark 5. Cache, throughput, and quality in KDA comparisons [ftip-00K7]AGENTDRAFTED
Remark 5. Cache, throughput, and quality in KDA comparisons [ftip-00K7]AGENTDRAFTED
The KDA example does not prove that every linear-attention model beats every Transformer, that cache savings imply equal quality, or that a measured throughput gain is a capability gain. Any such statement requires a new matched study with the evidence record of Definition [ftip-00JY].
Definition 6. Model-instance comparison decision rule [ftip-00K8]AGENTDRAFTED
Definition 6. Model-instance comparison decision rule [ftip-00K8]AGENTDRAFTED
Call architecture A more cost-efficient than B at quality \(q\) only when the compared threshold costs use the same declared protocol, the confidence procedure and stopping rule are fixed, and all cost-vector coordinates needed by the claim are present. A ratio additionally requires finite costs and a strictly positive denominator as in Definition [ftip-00JP]. State whether the costs are measured target-achieving witnesses or justified inverse-frontier values \(C_A(q)\) and \(C_B(q)\); observing one successful run does not identify those infima. Otherwise the comparison is descriptive or unknown.