<story><title>Profiling Go</title><url>http://www.integralist.co.uk/posts/profiling-go/</url></story><parent_chain></parent_chain><comment><author>d99kris</author><text>Slightly off-topic, but the web-based visualization tool - Chromium Catapult&amp;#x27;s Trace-viewer [0] - used to present the profiling data here is pretty nice I think.&lt;p&gt;The input JSON data format for Trace-viewer is also simple, so it&amp;#x27;s easy to to leverage it when creating a profiling tool. As a simple example I built a POSIX function call tracer for Linux - cpuusage [1] - which uses it.&lt;p&gt;[0]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;catapult-project&amp;#x2F;catapult&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;tracing&amp;#x2F;README.md&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;catapult-project&amp;#x2F;catapult&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;tra...&lt;/a&gt;&lt;p&gt;[1]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;d99kris&amp;#x2F;cpuusage&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;d99kris&amp;#x2F;cpuusage&lt;/a&gt;</text></comment>
<story><title>Profiling Go</title><url>http://www.integralist.co.uk/posts/profiling-go/</url></story><parent_chain></parent_chain><comment><author>jadeklerk</author><text>I found the original golang blog to be a fantastic resource on the topic: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.golang.org&amp;#x2F;profiling-go-programs&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.golang.org&amp;#x2F;profiling-go-programs&lt;/a&gt;</text></comment>