<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Speculative Decoding on Dhruv Patel - Lead Android Engineer</title><link>https://deardhruv.com/tags/speculative-decoding/</link><description>Recent content in Speculative Decoding on Dhruv Patel - Lead Android Engineer</description><generator>Hugo</generator><language>en</language><managingEditor>dhruv.time@gmail.com (Dhruv Patel)</managingEditor><webMaster>dhruv.time@gmail.com (Dhruv Patel)</webMaster><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener"&gt;CC BY-NC 4.0&lt;/a&gt;</copyright><lastBuildDate>Wed, 21 Oct 2026 18:04:07 +0530</lastBuildDate><atom:link href="https://deardhruv.com/tags/speculative-decoding/index.xml" rel="self" type="application/rss+xml"/><item><title>Part 6 - Pushing Mobile Hardware to the Edge</title><link>https://deardhruv.com/posts/ai_playground_series/06-pushing-mobile-hardware-to-the-edge/</link><pubDate>Wed, 21 Oct 2026 15:30:00 +0530</pubDate><author>dhruv.time@gmail.com (Dhruv Patel)</author><guid>https://deardhruv.com/posts/ai_playground_series/06-pushing-mobile-hardware-to-the-edge/</guid><description>&lt;h1 id="pushing-mobile-hardware-to-the-edge"&gt;Pushing Mobile Hardware to the Edge&lt;/h1&gt;
&lt;h2 id="part-6---dual-model-speculative-decoding-on-demand-gpu-dynamic-delivery-isolated-driver-crashes-and-streaming-fault-tolerance"&gt;Part 6 - Dual-model speculative decoding, on-demand GPU dynamic delivery, isolated driver crashes, and streaming fault-tolerance.&lt;/h2&gt;
&lt;p&gt;When you run open-source large language models on desktop GPUs, latency is rarely the bottleneck that keeps you awake at night. You have 24 GB of VRAM, 300 watts of wall power, and active cooling fans.&lt;/p&gt;
&lt;p&gt;On a smartphone, you have:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;a shared SoC memory pool
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;thermal throttling within minutes
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;aggressive OS process killers (Android LMK)
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;fragmented GPU drivers
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;a strict battery budget
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;In &lt;a href="https://deardhruv.com/posts/ai_playground_series/03-the-model-was-fine-the-phone-wasnt/"&gt;Part 3&lt;/a&gt;, we explored memory admission, quantization tradeoffs, and thermal guardrails. In &lt;a href="https://deardhruv.com/posts/ai_playground_series/05-at-some-point-i-stopped-building-a-chat-app/"&gt;Part 5&lt;/a&gt;, we established an MVI Clean Architecture to coordinate these moving parts.&lt;/p&gt;</description></item></channel></rss>