<?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>Cache-Coherence on Sandeep Kumar</title><link>https://sandeep007734.github.io/tags/cache-coherence/</link><description>Recent content in Cache-Coherence on Sandeep Kumar</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 10 Oct 2026 00:00:00 +0530</lastBuildDate><atom:link href="https://sandeep007734.github.io/tags/cache-coherence/feed.xml" rel="self" type="application/rss+xml"/><item><title>Why Innocent Shared Updates Stop Scaling: Cache Coherence on a Multi-Socket Server</title><link>https://sandeep007734.github.io/posts/cache_coherence/</link><pubDate>Tue, 03 Mar 2026 00:00:00 +0530</pubDate><guid>https://sandeep007734.github.io/posts/cache_coherence/</guid><description>How a one-line counter update turns into cross-core and cross-socket communication. Microbenchmarks on a dual-socket server separate local atomic cost, ownership handoffs, true sharing, and false sharing, and map each to a fix.</description></item></channel></rss>