<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Coz: Finding Code that Counts with Causal Profiling · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1608.03676/</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/1608.03676/feed.xml" rel="self" type="application/rss+xml" /><item><title>Coz: Finding Code that Counts with Causal Profiling — mentioned by sitkack</title><link>https://news.ycombinator.com/item?id=42810394</link><guid isPermaLink="false">urn:hackerpapers:mention:1608.03676:42810394</guid><pubDate>Fri, 24 Jan 2025 03:59:52 GMT</pubDate><description>&lt;p&gt;If you enjoy the science of injecting slowness to determine which component has the largest impact on performance, you would enjoy this work by Emery Berger. Coz: Finding Code that Counts with Causal Profiling https://arxiv.org/abs/1608.03676 &amp;quot;Performance (Really) Matters&amp;quot; with Emery Berger https://www.youtube.com/watch?v=7g1Acy5eGbE&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1608.03676/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PF</category></item><item><title>Coz: Finding Code that Counts with Causal Profiling — mentioned by moonchild</title><link>https://news.ycombinator.com/item?id=23634511</link><guid isPermaLink="false">urn:hackerpapers:mention:1608.03676:23634511</guid><pubDate>Wed, 24 Jun 2020 22:19:09 GMT</pubDate><description>&lt;p&gt;&amp;gt; deleting this one line of code can have a dramatic effect on seemingly unrelated performance micro-benchmarks. Some numbers get better (e.g. +5%), some numbers get worse (e.g. -10%). The same micro-benchmark can get faster on one C compiler but slower on another There&amp;#x27;s a fundamental disconnect that makes it difficult for humans to reason about performance in computer programs. Because the speed of light is so slow, computer architecture as we know it will always rely on cache and OoO to be fast. The human brain does seem to work out of order, but it&amp;#x27;s only used to thinking about a world…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1608.03676/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PF</category></item><item><title>Coz: Finding Code that Counts with Causal Profiling — mentioned by vlovich123</title><link>https://news.ycombinator.com/item?id=22405344</link><guid isPermaLink="false">urn:hackerpapers:mention:1608.03676:22405344</guid><pubDate>Mon, 24 Feb 2020 16:15:22 GMT</pubDate><description>&lt;p&gt;There&amp;#x27;s also something to be said for building better tooling in this area. Not everyone can achieve expertise in everything. Better tooling helps level the playing feel (&amp;amp; eventually outperform experts when the tooling becomes indispensable). You may think that&amp;#x27;s a cop-out, but consider something like coz[1]. Sqlite is managed and maintained by experts. There&amp;#x27;s significant capital behind investing engineering effort. However, better tooling still managed to locate 25% of performance improvement[2] &amp;amp; even 9% in memcached. Even experts have their limits &amp;amp; of course these tools require…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1608.03676/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PF</category></item></channel></rss>
