<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Profiling on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/profiling/</link>
    <description>Recent content in Profiling on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 01 Apr 2020 10:18:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/profiling/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Profiling Go Services in Production with pprof</title>
      <link>https://blog.turboawesome.win/2020/04/profiling-go-services-in-production-with-pprof/</link>
      <pubDate>Wed, 01 Apr 2020 10:18:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2020/04/profiling-go-services-in-production-with-pprof/</guid>
      <description>Go&amp;#39;s pprof tooling is built in, low-overhead, and more useful than most engineers realise. Here&amp;#39;s how to capture CPU and memory profiles from production services and actually read what they tell you.</description>
    </item>
    <item>
      <title>Go Benchmarks: Writing Ones That Actually Tell You Something</title>
      <link>https://blog.turboawesome.win/2020/03/go-benchmarks-writing-ones-that-actually-tell-you-something/</link>
      <pubDate>Tue, 17 Mar 2020 09:29:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2020/03/go-benchmarks-writing-ones-that-actually-tell-you-something/</guid>
      <description>Go&amp;#39;s built-in benchmark framework is excellent, but it&amp;#39;s easy to write benchmarks that measure the wrong thing — compiler optimisations, cache warming artifacts, or benchmark overhead rather than the code under test.</description>
    </item>
    <item>
      <title>Heap Dumps and Flight Recorder: Diagnosing JVM Memory Problems in Production</title>
      <link>https://blog.turboawesome.win/2016/08/heap-dumps-and-flight-recorder-diagnosing-jvm-memory-problems-in-production/</link>
      <pubDate>Wed, 24 Aug 2016 14:55:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2016/08/heap-dumps-and-flight-recorder-diagnosing-jvm-memory-problems-in-production/</guid>
      <description>Heap dumps and Java Flight Recorder are the two tools that diagnose production JVM memory problems. Understanding how to capture them without killing the service, and how to read what they tell you, is a gap in most JVM engineers&amp;#39; toolkits.</description>
    </item>
    <item>
      <title>Why Average Latency Is a Lie: HdrHistogram and Measuring What Matters</title>
      <link>https://blog.turboawesome.win/2013/11/why-average-latency-is-a-lie-hdrhistogram-and-measuring-what-matters/</link>
      <pubDate>Wed, 27 Nov 2013 11:14:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2013/11/why-average-latency-is-a-lie-hdrhistogram-and-measuring-what-matters/</guid>
      <description>Average latency hides the distribution. HdrHistogram gives you a complete picture of latency across the full range — and it does so without distorting the system you&amp;#39;re measuring.</description>
    </item>
  </channel>
</rss>
