<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>On Large-Batch Training for Deep Learning: Generalization Gap and Sharp Minima · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1609.04836/</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/1609.04836/feed.xml" rel="self" type="application/rss+xml" /><item><title>On Large-Batch Training for Deep Learning: Generalization Gap and Sharp Minima — mentioned by blackbear_</title><link>https://news.ycombinator.com/item?id=45788604</link><guid isPermaLink="false">urn:hackerpapers:mention:1609.04836:45788604</guid><pubDate>Sun, 02 Nov 2025 07:51:40 GMT</pubDate><description>&lt;p&gt;Two thoughts: &amp;gt; how important is computing the exact gradient using calculus Normally the gradient is computed with a small &amp;quot;minibatch&amp;quot; of examples, meaning that on average over many steps the true gradient is followed, but each step individually never moves exacty along the true gradient. This noisy walk is actually quite beneficial for the final performance of the network https://arxiv.org/abs/2006.15081 , https://arxiv.org/abs/1609.04836 so much so that people started wondering what is the best way to &amp;quot;corrupt&amp;quot; this approximate gradient even more to improve performance…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1609.04836/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item><item><title>On Large-Batch Training for Deep Learning: Generalization Gap and Sharp Minima — mentioned by chillee</title><link>https://news.ycombinator.com/item?id=15956040</link><guid isPermaLink="false">urn:hackerpapers:mention:1609.04836:15956040</guid><pubDate>Mon, 18 Dec 2017 22:20:36 GMT</pubDate><description>&lt;p&gt;Sorry, my last sentence &amp;gt; Otherwise, models can achieve very good generalization. was probably unclear. When we talk about generalization, we typically have to assume a lack of distributional shift. Otherwise, if the &amp;quot;truly unseen data&amp;quot; really is drawn from a different distribution (say one where all cats are now called &amp;quot;dogs&amp;quot; and all dogs are now called &amp;quot;cats&amp;quot;), we can get arbitrarily poor performance. As for the flat minima part, lemme pull up some papers from my notes. https://arxiv.org/abs/1609.04836 showed larger batch sizes lead to sharper minima. &amp;gt; ... and as is well known, sharp…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1609.04836/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item><item><title>On Large-Batch Training for Deep Learning: Generalization Gap and Sharp Minima — mentioned by chillee</title><link>https://news.ycombinator.com/item?id=15912167</link><guid isPermaLink="false">urn:hackerpapers:mention:1609.04836:15912167</guid><pubDate>Wed, 13 Dec 2017 05:10:04 GMT</pubDate><description>&lt;p&gt;Really don&amp;#x27;t think that&amp;#x27;s the best paper to say &amp;quot;sheds quite a bit of light on this&amp;quot;. That paper has been somewhat controversial since it came out. I think https://arxiv.org/abs/1609.04836 is seminal in showing unsharp minima = generalization, the parent&amp;#x27;s paper is good for showing that gradient descent over non-convex surfaces works fine, https://arxiv.org/abs/1611.03530 is landmark for kicking off this whole generalization business (mainly shows that traditional models of generalization, namely VC dimension and ideas of &amp;quot;capacity&amp;quot; don&amp;#x27;t make sense for neural nets).&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1609.04836/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item><item><title>On Large-Batch Training for Deep Learning: Generalization Gap and Sharp Minima — mentioned by IanCal</title><link>https://news.ycombinator.com/item?id=14543719</link><guid isPermaLink="false">urn:hackerpapers:mention:1609.04836:14543719</guid><pubDate>Tue, 13 Jun 2017 09:35:17 GMT</pubDate><description>&lt;p&gt;&amp;gt; shouldn&amp;#x27;t a larger batch_size inherently provide more information about the optimal direction of the update? Not necessarily, since a batch gradient output (as I understand it, and at least used to code it) all gets averaged together. Consider standing in a valley with two equal hills either side of you. If you were to try one direction and see that climbing that way helps, you&amp;#x27;d take a step that way. Then the next step would keep taking you up that hill. Now, if you batched together two direction tests, what would happen? You&amp;#x27;d average together your left and right and end up with moving…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1609.04836/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item><item><title>On Large-Batch Training for Deep Learning: Generalization Gap and Sharp Minima — mentioned by mijoharas</title><link>https://news.ycombinator.com/item?id=13939121</link><guid isPermaLink="false">urn:hackerpapers:mention:1609.04836:13939121</guid><pubDate>Thu, 23 Mar 2017 12:22:00 GMT</pubDate><description>&lt;p&gt;My understanding from this article is that for a greater GPU ram size you will need to increase the minibatch size which has a negative impact on the models ability to generalize[0]. [0] https://arxiv.org/abs/1609.04836&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1609.04836/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item><item><title>On Large-Batch Training for Deep Learning: Generalization Gap and Sharp Minima — mentioned by ogrisel</title><link>https://news.ycombinator.com/item?id=13018048</link><guid isPermaLink="false">urn:hackerpapers:mention:1609.04836:13018048</guid><pubDate>Tue, 22 Nov 2016 21:58:24 GMT</pubDate><description>&lt;p&gt;Then the total batch size is growing with the number of GPUs and the convergence might be impacted both in terms of speed and solution quality (e.g. https://arxiv.org/abs/1609.04836 ). I could believe you if tell you me that the validation loss and test accuracy of the large distributed model remains as good as the sequential, single GPU model after the same total number of epochs but this is not a given and if it&amp;#x27;s not the case I would find those benchmarks deceptive.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1609.04836/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item></channel></rss>
