<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Code Analysis - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Code Analysis Articles feed</description>
    <item>
      <title>Article: Debugging Go Code: Using pprof and trace to Diagnose and Fix Performance Issues</title>
      <link>https://www.infoq.com/articles/debugging-go-programs-pprof-trace/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Code+Analysis-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/debugging-go-programs-pprof-trace/en/headerimage/debugging-g-code-using-pprof-and-trace-to-diagnose-and-fix-performance-header-1686564312552.jpg"/&gt;&lt;p&gt;In this article, we will look at how to identify and fix performance issues in Go programs using the pprof and trace packages. We will begin by covering the fundamentals of the tools, then delving into practical examples of how to use them.  By the end of this article, you will have a solid understanding of how to use these powerful tools to improve the performance of your Go applications.&lt;/p&gt; &lt;i&gt;By Oghenevwede Emeni&lt;/i&gt;</description>
      <category>Cost Optimization</category>
      <category>Concurrency</category>
      <category>Go Language</category>
      <category>Code Analysis</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Thu, 15 Jun 2023 09:05:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/debugging-go-programs-pprof-trace/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Code+Analysis-articles</guid>
      <dc:creator>Oghenevwede Emeni</dc:creator>
      <dc:date>2023-06-15T09:05:00Z</dc:date>
      <dc:identifier>/articles/debugging-go-programs-pprof-trace/en</dc:identifier>
    </item>
  </channel>
</rss>
