<?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>Memory on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/memory/</link>
    <description>Recent content in Memory on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 17 Aug 2022 10:03:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/memory/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Memory Layout in Go: Structs, Alignment, and Cache Performance</title>
      <link>https://blog.turboawesome.win/2022/08/memory-layout-in-go-structs-alignment-and-cache-performance/</link>
      <pubDate>Wed, 17 Aug 2022 10:03:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2022/08/memory-layout-in-go-structs-alignment-and-cache-performance/</guid>
      <description>Go&amp;#39;s struct layout follows alignment rules that affect both memory consumption and cache performance. Understanding them matters more than most Go developers realise.</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>Memory-Mapped Files in Java: Chronicle and the Art of Zero-Copy I/O</title>
      <link>https://blog.turboawesome.win/2015/04/memory-mapped-files-in-java-chronicle-and-the-art-of-zero-copy-i/o/</link>
      <pubDate>Wed, 15 Apr 2015 09:53:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2015/04/memory-mapped-files-in-java-chronicle-and-the-art-of-zero-copy-i/o/</guid>
      <description>Memory-mapped files let you treat disk storage as if it&amp;#39;s RAM — the OS handles the mapping and caching transparently. Chronicle Queue uses this to give you a persistent ordered log with throughput approaching raw memory bandwidth.</description>
    </item>
    <item>
      <title>Off-Heap Memory in Java: sun.misc.Unsafe and Chronicle Map</title>
      <link>https://blog.turboawesome.win/2014/04/off-heap-memory-in-java-sun.misc.unsafe-and-chronicle-map/</link>
      <pubDate>Wed, 02 Apr 2014 10:17:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2014/04/off-heap-memory-in-java-sun.misc.unsafe-and-chronicle-map/</guid>
      <description>The Java heap is GC&amp;#39;d. Off-heap memory is not. For large data structures that don&amp;#39;t benefit from GC management and do benefit from predictable latency, off-heap allocation via Unsafe and Chronicle Map is the right tool — if you respect its dangers.</description>
    </item>
    <item>
      <title>Disruptor Deep Dive: Memory Layout, Cache Lines, and False Sharing</title>
      <link>https://blog.turboawesome.win/2013/04/disruptor-deep-dive-memory-layout-cache-lines-and-false-sharing/</link>
      <pubDate>Tue, 09 Apr 2013 11:27:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2013/04/disruptor-deep-dive-memory-layout-cache-lines-and-false-sharing/</guid>
      <description>Why the Disruptor is fast is inseparable from how it&amp;#39;s laid out in memory. A ground-up look at the cache line strategy that makes the numbers possible.</description>
    </item>
  </channel>
</rss>
