<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Query-Key Normalization for Transformers · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2010.04245/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2010.04245/feed.xml" rel="self" type="application/rss+xml" /><item><title>Query-Key Normalization for Transformers — mentioned by kouteiheika</title><link>https://news.ycombinator.com/item?id=44076133</link><guid isPermaLink="false">urn:hackerpapers:mention:2010.04245:44076133</guid><pubDate>Fri, 23 May 2025 20:03:30 GMT</pubDate><description>&lt;p&gt;&amp;gt; Let&amp;#x27;s look at some of the most important ones that have been developed over the years and try to implement the basic ideas as succinctly as possible. One big architectural tweak that comes to mind and isn&amp;#x27;t in the article is QK norm: https://arxiv.org/pdf/2010.04245 &amp;gt; Cosine Schedule A lot (most?) of new training runs actually don&amp;#x27;t use cosine schedule anymore; instead they keep the learning rate constant and only decay it at the very end, which gives equivalent or better results. See: https://arxiv.org/pdf/2405.18392 https://arxiv.org/pdf/2404.06395 &amp;gt; There is a highly optimized…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2010.04245/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>Query-Key Normalization for Transformers — mentioned by mota7</title><link>https://news.ycombinator.com/item?id=41781277</link><guid isPermaLink="false">urn:hackerpapers:mention:2010.04245:41781277</guid><pubDate>Tue, 08 Oct 2024 20:04:15 GMT</pubDate><description>&lt;p&gt;I had the same thought: Just eye-balling the graphs, the result of the subtraction looks very close to just reducing the temperature. They&amp;#x27;re effectively doing softmax with a fixed temperature, but it&amp;#x27;s unclear that this work is going to do better than just learning a per-head temperature parameter. c.f. https://arxiv.org/abs/2010.04245 which shows an improvement by learning per-head temperature. The other way to think about this is that it looks like a hacked-up kinda-sorta gated attention. If that&amp;#x27;s the case, then doing softmax(alphaq_1k_1^T - log_sigmoid(betaq_2k_2^T)) might be better?…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2010.04245/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item></channel></rss>
