<story><title>Multi-process Firefox brings 400-700% improvement in responsiveness</title><url>https://techcrunch.com/2016/09/02/multi-process-firefox-brings-400-700-improvement-in-responsiveness/</url></story><parent_chain><item><author>azinman2</author><text>Maybe I&amp;#x27;m misreading things but it looks like it&amp;#x27;s been constantly getting worse since 2012?</text></item><item><author>AdmiralAsshat</author><text>And they&amp;#x27;re still at it, too:
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;areweslimyet.com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;areweslimyet.com&amp;#x2F;&lt;/a&gt;</text></item><item><author>toxican</author><text>A few years ago if you&amp;#x27;d told me FF would be the RAM-sensitive browser, I&amp;#x27;d have laughed you off the internet.</text></item><item><author>rsp1984</author><text>&lt;i&gt;“We can learn from the competition,” said Dotzler. “The way they implemented multi-process is RAM-intensive, it can get out of hand. We are learning from them and building an architecture that doesn’t eat all your RAM.”&lt;/i&gt;&lt;p&gt;That&amp;#x27;s the money quote here. I&amp;#x27;ve been waiting for this for a long time actually. Every browser I&amp;#x27;ve tried except Firefox just basically eats all my RAM and other app performance (e.g. compiling stuff) goes down the toilet.&lt;p&gt;Then on the other hand FF has not been so snappy and responsive traditionally. So responsive + soft on RAM is the combination I&amp;#x27;ve really been waiting for. Let&amp;#x27;s hope they can deliver.</text></item></parent_chain><comment><author>Lagged2Death</author><text>The FAQ says:&lt;p&gt;&lt;i&gt;TP5 loads 100 popular webpages, served from a local webserver.&lt;/i&gt;&lt;p&gt;I don&amp;#x27;t know if that means the test pages are up-to-date copies of real-world pages or not. On one hand, real-world pages have certainly been getting heavier, and it would bear mentioning if that fact was not reflected in this test. On the other hand the graph becomes really hard to interpret if the test suite isn&amp;#x27;t a constant.</text></comment>
<story><title>Multi-process Firefox brings 400-700% improvement in responsiveness</title><url>https://techcrunch.com/2016/09/02/multi-process-firefox-brings-400-700-improvement-in-responsiveness/</url></story><parent_chain><item><author>azinman2</author><text>Maybe I&amp;#x27;m misreading things but it looks like it&amp;#x27;s been constantly getting worse since 2012?</text></item><item><author>AdmiralAsshat</author><text>And they&amp;#x27;re still at it, too:
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;areweslimyet.com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;areweslimyet.com&amp;#x2F;&lt;/a&gt;</text></item><item><author>toxican</author><text>A few years ago if you&amp;#x27;d told me FF would be the RAM-sensitive browser, I&amp;#x27;d have laughed you off the internet.</text></item><item><author>rsp1984</author><text>&lt;i&gt;“We can learn from the competition,” said Dotzler. “The way they implemented multi-process is RAM-intensive, it can get out of hand. We are learning from them and building an architecture that doesn’t eat all your RAM.”&lt;/i&gt;&lt;p&gt;That&amp;#x27;s the money quote here. I&amp;#x27;ve been waiting for this for a long time actually. Every browser I&amp;#x27;ve tried except Firefox just basically eats all my RAM and other app performance (e.g. compiling stuff) goes down the toilet.&lt;p&gt;Then on the other hand FF has not been so snappy and responsive traditionally. So responsive + soft on RAM is the combination I&amp;#x27;ve really been waiting for. Let&amp;#x27;s hope they can deliver.</text></item></parent_chain><comment><author>arcatek</author><text>There&amp;#x27;s more and more features every month. Add that to the various performance improvements (that can take a hit on the ram, dependending on how they&amp;#x27;re implemented), and it becomes a bit more understandable why you would see such an increase.</text></comment>