<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hardware on Chandan Kumar Dash</title><link>https://ckdash.com/tags/hardware/</link><description>Recent content in Hardware on Chandan Kumar Dash</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ckdash.com/tags/hardware/index.xml" rel="self" type="application/rss+xml"/><item><title>Why MacBooks Have Longer Battery Life</title><link>https://ckdash.com/blogs/macbook-unified-memory/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://ckdash.com/blogs/macbook-unified-memory/</guid><description>&lt;p&gt;Once, while browsing a MacBook&amp;rsquo;s specs on Apple&amp;rsquo;s website, I noticed something odd. Instead of &lt;strong&gt;&amp;ldquo;16 GB RAM&amp;rdquo;&lt;/strong&gt;, it said &lt;strong&gt;&amp;ldquo;16 GB Unified Memory&amp;rdquo;&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;I rolled my eyes. Classic Apple — slapping a fancy name on something ordinary to justify a premium price. But I Googled it anyway.&lt;/p&gt;
&lt;p&gt;What I found completely changed how I think about computer hardware. And I&amp;rsquo;d bet that once you understand it too, your next laptop might just be a MacBook.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="the-traditional-setup-two-chips-two-memories"&gt;The Traditional Setup: Two Chips, Two Memories
&lt;/h2&gt;&lt;p&gt;Most Windows laptops (and older Macs) use a conventional architecture with two separate processors:&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Processor&lt;/th&gt;
&lt;th&gt;Role&lt;/th&gt;
&lt;th&gt;Strength&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;CPU&lt;/strong&gt; (Central Processing Unit)&lt;/td&gt;
&lt;td&gt;General-purpose computation&lt;/td&gt;
&lt;td&gt;Handles complex, sequential tasks with high intelligence&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;GPU&lt;/strong&gt; (Graphics Processing Unit)&lt;/td&gt;
&lt;td&gt;Parallel computation&lt;/td&gt;
&lt;td&gt;Runs thousands of simple operations simultaneously&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;Think of a &lt;strong&gt;CPU&lt;/strong&gt; as a brilliant professor who solves problems one by one, with great depth. A &lt;strong&gt;GPU&lt;/strong&gt; is more like a stadium full of workers, each doing one small thing — but all at the same time.&lt;/p&gt;
&lt;p&gt;This division makes sense. Some problems, like rendering graphics or training a neural network, require massive parallelism. The GPU excels here. The CPU kicks off the task and delegates.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="a-concrete-example-matrix-multiplication"&gt;A Concrete Example: Matrix Multiplication
&lt;/h2&gt;&lt;p&gt;Machine learning — which runs everything from Siri to your photo suggestions — relies heavily on &lt;strong&gt;matrix multiplication&lt;/strong&gt;. When you multiply two 1,000 × 1,000 matrices, you&amp;rsquo;re performing &lt;strong&gt;one billion individual calculations&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;A CPU would crank through those row-by-column multiplications sequentially, taking a noticeable amount of time. A GPU can blast through the same problem in a fraction of a second by doing thousands of multiplications in parallel.&lt;/p&gt;
&lt;p&gt;So the CPU says: &lt;em&gt;&amp;ldquo;Here, GPU — you handle this.&amp;rdquo;&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="the-hidden-cost-crossing-the-bridge"&gt;The Hidden Cost: Crossing the Bridge
&lt;/h2&gt;&lt;p&gt;Here&amp;rsquo;s where the problem lives.&lt;/p&gt;
&lt;p&gt;The CPU stores its data in &lt;strong&gt;RAM&lt;/strong&gt;. The GPU stores its data in &lt;strong&gt;VRAM&lt;/strong&gt; (Video RAM). These are physically separate chips, connected by a high-speed &lt;strong&gt;PCI Express&lt;/strong&gt; (PCIe) lane.&lt;/p&gt;
&lt;p&gt;Before the GPU can start multiplying those matrices, the CPU must &lt;strong&gt;copy both matrices from RAM into VRAM&lt;/strong&gt;. After the GPU finishes, the result gets &lt;strong&gt;copied back&lt;/strong&gt; through the same PCIe lane into RAM.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#282a36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;1&lt;/span&gt;&lt;span&gt;CPU (RAM) ──── PCIe Lane ────▶ GPU (VRAM)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;2&lt;/span&gt;&lt;span&gt; [data copy]
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;3&lt;/span&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;4&lt;/span&gt;&lt;span&gt;GPU (VRAM) ─── PCIe Lane ────▶ CPU (RAM)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;5&lt;/span&gt;&lt;span&gt; [result copy]
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This round-trip causes two serious problems:&lt;/p&gt;
&lt;h3 id="-problem-1-latency"&gt;⏱ Problem 1: Latency
&lt;/h3&gt;&lt;p&gt;Copying large datasets back and forth takes time — time that your app, your model, or your game has to &lt;em&gt;wait&lt;/em&gt;.&lt;/p&gt;
&lt;h3 id="-problem-2-power--heat"&gt;🔥 Problem 2: Power &amp;amp; Heat
&lt;/h3&gt;&lt;p&gt;PCIe data transfers consume significant electricity. That electricity becomes heat. In a thin laptop chassis, that heat has nowhere to go — triggering &lt;strong&gt;thermal throttling&lt;/strong&gt;, where the processor slows itself down to cool off. You&amp;rsquo;ve felt this: the fan screams, the laptop scorches your lap, and everything starts lagging.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="apples-fix-unified-memory-architecture"&gt;Apple&amp;rsquo;s Fix: Unified Memory Architecture
&lt;/h2&gt;&lt;p&gt;Apple didn&amp;rsquo;t just tweak the design. They rethought it entirely.&lt;/p&gt;
&lt;p&gt;With &lt;strong&gt;Apple Silicon&lt;/strong&gt; (M-series chips), Apple placed the &lt;strong&gt;CPU, GPU, and Neural Engine all on a single chip&lt;/strong&gt; — and attached a single, shared pool of memory to all of them.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#282a36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 1&lt;/span&gt;&lt;span&gt;┌─────────────────────────────────────────┐
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 2&lt;/span&gt;&lt;span&gt;│ Apple Silicon │
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 3&lt;/span&gt;&lt;span&gt;│ │
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 4&lt;/span&gt;&lt;span&gt;│ ┌───────┐ ┌───────┐ ┌───────────┐ │
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 5&lt;/span&gt;&lt;span&gt;│ │ CPU │ │ GPU │ │ Neural │ │
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 6&lt;/span&gt;&lt;span&gt;│ │ │ │ │ │ Engine │ │
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 7&lt;/span&gt;&lt;span&gt;│ └───┬───┘ └───┬───┘ └─────┬─────┘ │
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 8&lt;/span&gt;&lt;span&gt;│ │ │ │ │
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt; 9&lt;/span&gt;&lt;span&gt;│ ════╪══════════╪════════════╪════ │
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;10&lt;/span&gt;&lt;span&gt;│ Unified Memory │
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;11&lt;/span&gt;&lt;span&gt;└─────────────────────────────────────────┘
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This is &lt;strong&gt;Unified Memory Architecture (UMA)&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Now, when the CPU needs the GPU to multiply those matrices, it doesn&amp;rsquo;t copy anything. It simply passes the &lt;strong&gt;memory address&lt;/strong&gt; — a pointer — to where the data already lives. The GPU reads directly from the same memory the CPU uses.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#282a36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-fallback" data-lang="fallback"&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;1&lt;/span&gt;&lt;span&gt;CPU ──── passes memory pointer ────▶ GPU
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;2&lt;/span&gt;&lt;span&gt; (no data copied)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;3&lt;/span&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;4&lt;/span&gt;&lt;span&gt;GPU ──── returns result pointer ────▶ CPU
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;5&lt;/span&gt;&lt;span&gt; (no data copied)
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The data never moves. Only the &lt;em&gt;reference&lt;/em&gt; to the data is shared.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="why-this-changes-everything"&gt;Why This Changes Everything
&lt;/h2&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Traditional Architecture&lt;/th&gt;
&lt;th&gt;Apple Unified Memory&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Data transfer&lt;/td&gt;
&lt;td&gt;Copy entire datasets via PCIe&lt;/td&gt;
&lt;td&gt;Pass a memory pointer&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Latency&lt;/td&gt;
&lt;td&gt;High (copy takes time)&lt;/td&gt;
&lt;td&gt;Near-zero&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Power draw&lt;/td&gt;
&lt;td&gt;High (PCIe transfers)&lt;/td&gt;
&lt;td&gt;Minimal&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Heat generated&lt;/td&gt;
&lt;td&gt;Significant&lt;/td&gt;
&lt;td&gt;Very low&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Need for cooling fan&lt;/td&gt;
&lt;td&gt;Yes (most laptops)&lt;/td&gt;
&lt;td&gt;MacBook Air: &lt;strong&gt;none&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Battery life&lt;/td&gt;
&lt;td&gt;Limited by thermals&lt;/td&gt;
&lt;td&gt;Industry-leading&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;No heat means no thermal throttling. No thermal throttling means sustained performance. Sustained performance on less power means a battery that lasts all day.&lt;/p&gt;
&lt;p&gt;This is why the &lt;strong&gt;MacBook Air has no cooling fan&lt;/strong&gt; — not because Apple cut corners, but because the chip generates so little heat that active cooling is simply unnecessary.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="the-honest-trade-off"&gt;The Honest Trade-off
&lt;/h2&gt;&lt;p&gt;Unified Memory isn&amp;rsquo;t magic without compromise. Because all components share the same physical memory, what Apple sells as &amp;ldquo;16 GB Unified Memory&amp;rdquo; has to cover both your system RAM &lt;em&gt;and&lt;/em&gt; your GPU memory. On a traditional machine, you might have 16 GB RAM &lt;em&gt;plus&lt;/em&gt; 8 GB dedicated VRAM.&lt;/p&gt;
&lt;p&gt;For most people — students, developers, creatives, professionals — 16 or 24 GB of Unified Memory is more than enough. The raw efficiency of the architecture more than compensates. But for extreme GPU workloads (think: training large models locally), dedicated VRAM still has its place.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="what-changed-my-mind"&gt;What Changed My Mind
&lt;/h2&gt;&lt;p&gt;I started with the assumption that &amp;ldquo;Unified Memory&amp;rdquo; was a rebrand of ordinary RAM. It isn&amp;rsquo;t. It&amp;rsquo;s a fundamentally different architecture that eliminates an entire class of bottleneck.&lt;/p&gt;
&lt;p&gt;The result? A laptop that runs cooler, lasts longer, and performs faster — not because it has the biggest numbers on a spec sheet, but because the &lt;em&gt;design&lt;/em&gt; is smarter.&lt;/p&gt;
&lt;p&gt;Sometimes the best engineering is invisible. You just notice that the battery icon never seems to drop.&lt;/p&gt;</description></item></channel></rss>