<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bandwidth on Jasper</title><link>https://jasper-aa64.github.io/tags/bandwidth/</link><description>Recent content in Bandwidth on Jasper</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 09 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://jasper-aa64.github.io/tags/bandwidth/index.xml" rel="self" type="application/rss+xml"/><item><title>Low-Latency Trading — Memory Latency and Bandwidth</title><link>https://jasper-aa64.github.io/posts/low-latency-memory-latency-bandwidth/</link><pubDate>Fri, 09 Oct 2026 00:00:00 +0000</pubDate><guid>https://jasper-aa64.github.io/posts/low-latency-memory-latency-bandwidth/</guid><description>One memory access takes about 100 ns and brings back 64 B. One at a time, that&amp;rsquo;s 0.64 GB/s, yet one core reading sequentially gets 15–60 GB/s. The missing factor is the number of requests in flight. Whether the next load&amp;rsquo;s address has to wait for this load decides whether your code is latency-bound or bandwidth-bound.</description></item></channel></rss>