<?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>并发控制 on Answer</title>
    <link>https://answer.freetools.me/tags/%E5%B9%B6%E5%8F%91%E6%8E%A7%E5%88%B6/</link>
    <description>Recent content in 并发控制 on Answer</description>
    <generator>Hugo -- 0.152.2</generator>
    <language>zh-cn</language>
    <lastBuildDate>Wed, 11 Mar 2026 06:14:16 +0800</lastBuildDate>
    <atom:link href="https://answer.freetools.me/tags/%E5%B9%B6%E5%8F%91%E6%8E%A7%E5%88%B6/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Web Locks API：浏览器如何让多标签页优雅地协调资源</title>
      <link>https://answer.freetools.me/web-locks-api%E6%B5%8F%E8%A7%88%E5%99%A8%E5%A6%82%E4%BD%95%E8%AE%A9%E5%A4%9A%E6%A0%87%E7%AD%BE%E9%A1%B5%E4%BC%98%E9%9B%85%E5%9C%B0%E5%8D%8F%E8%B0%83%E8%B5%84%E6%BA%90/</link>
      <pubDate>Wed, 11 Mar 2026 06:14:16 +0800</pubDate>
      <guid>https://answer.freetools.me/web-locks-api%E6%B5%8F%E8%A7%88%E5%99%A8%E5%A6%82%E4%BD%95%E8%AE%A9%E5%A4%9A%E6%A0%87%E7%AD%BE%E9%A1%B5%E4%BC%98%E9%9B%85%E5%9C%B0%E5%8D%8F%E8%B0%83%E8%B5%84%E6%BA%90/</guid>
      <description>深入解析 Web Locks API 的设计哲学与实现原理：从跨标签页协调的困境出发，剖析传统方案的局限性，详解锁请求、锁管理器、调度算法等核心机制，对比 localStorage、BroadcastChannel、SharedWorker 等替代方案，揭示浏览器如何在同一源内实现可靠的锁机制。</description>
    </item>
    <item>
      <title>数据库死锁为何如此难以根除从检测算法到预防策略的五十年博弈</title>
      <link>https://answer.freetools.me/%E6%95%B0%E6%8D%AE%E5%BA%93%E6%AD%BB%E9%94%81%E4%B8%BA%E4%BD%95%E5%A6%82%E6%AD%A4%E9%9A%BE%E4%BB%A5%E6%A0%B9%E9%99%A4%E4%BB%8E%E6%A3%80%E6%B5%8B%E7%AE%97%E6%B3%95%E5%88%B0%E9%A2%84%E9%98%B2%E7%AD%96%E7%95%A5%E7%9A%84%E4%BA%94%E5%8D%81%E5%B9%B4%E5%8D%9A%E5%BC%88/</link>
      <pubDate>Sat, 07 Mar 2026 01:56:28 +0800</pubDate>
      <guid>https://answer.freetools.me/%E6%95%B0%E6%8D%AE%E5%BA%93%E6%AD%BB%E9%94%81%E4%B8%BA%E4%BD%95%E5%A6%82%E6%AD%A4%E9%9A%BE%E4%BB%A5%E6%A0%B9%E9%99%A4%E4%BB%8E%E6%A3%80%E6%B5%8B%E7%AE%97%E6%B3%95%E5%88%B0%E9%A2%84%E9%98%B2%E7%AD%96%E7%95%A5%E7%9A%84%E4%BA%94%E5%8D%81%E5%B9%B4%E5%8D%9A%E5%BC%88/</guid>
      <description>深入剖析数据库死锁检测与预防的五十年技术演进：从Coffman四个必要条件到Wait-for Graph检测算法，从Wait-Die/Wound-Wait预防策略到MySQL、PostgreSQL、SQL Server的实现差异。基于IEEE/ACM论文、官方文档和真实生产案例，系统梳理死锁检测的开销与权衡，以及应用层如何设计才能从根本上避免死锁。</description>
    </item>
    <item>
      <title>数据库连接池不是越大越好：为什么10个连接能击败100个</title>
      <link>https://answer.freetools.me/%E6%95%B0%E6%8D%AE%E5%BA%93%E8%BF%9E%E6%8E%A5%E6%B1%A0%E4%B8%8D%E6%98%AF%E8%B6%8A%E5%A4%A7%E8%B6%8A%E5%A5%BD%E4%B8%BA%E4%BB%80%E4%B9%8810%E4%B8%AA%E8%BF%9E%E6%8E%A5%E8%83%BD%E5%87%BB%E8%B4%A5100%E4%B8%AA/</link>
      <pubDate>Fri, 06 Mar 2026 22:09:20 +0800</pubDate>
      <guid>https://answer.freetools.me/%E6%95%B0%E6%8D%AE%E5%BA%93%E8%BF%9E%E6%8E%A5%E6%B1%A0%E4%B8%8D%E6%98%AF%E8%B6%8A%E5%A4%A7%E8%B6%8A%E5%A5%BD%E4%B8%BA%E4%BB%80%E4%B9%8810%E4%B8%AA%E8%BF%9E%E6%8E%A5%E8%83%BD%E5%87%BB%E8%B4%A5100%E4%B8%AA/</guid>
      <description>从Oracle Real World Performance Group的震撼实验说起，深度剖析数据库连接池配置的反直觉真相。基于HikariCP官方Wiki、PostgreSQL性能基准测试、USENIX Security论文等50&#43;权威信源，揭示连接池大小为何存在性能拐点、上下文切换如何吞噬性能、以及核心数×2&#43;磁盘数公式的数学原理。涵盖连接泄漏检测、超时配置陷阱、PgBouncer三种池模式对比、云原生环境挑战等实战经验，为开发者提供从理论到实践的完整配置指南。</description>
    </item>
    <item>
      <title>分布式锁为何成了生产事故的隐形杀手——从Martin Kleppmann与antirez的论战说起</title>
      <link>https://answer.freetools.me/%E5%88%86%E5%B8%83%E5%BC%8F%E9%94%81%E4%B8%BA%E4%BD%95%E6%88%90%E4%BA%86%E7%94%9F%E4%BA%A7%E4%BA%8B%E6%95%85%E7%9A%84%E9%9A%90%E5%BD%A2%E6%9D%80%E6%89%8B%E4%BB%8Emartin-kleppmann%E4%B8%8Eantirez%E7%9A%84%E8%AE%BA%E6%88%98%E8%AF%B4%E8%B5%B7/</link>
      <pubDate>Fri, 06 Mar 2026 16:45:00 +0800</pubDate>
      <guid>https://answer.freetools.me/%E5%88%86%E5%B8%83%E5%BC%8F%E9%94%81%E4%B8%BA%E4%BD%95%E6%88%90%E4%BA%86%E7%94%9F%E4%BA%A7%E4%BA%8B%E6%95%85%E7%9A%84%E9%9A%90%E5%BD%A2%E6%9D%80%E6%89%8B%E4%BB%8Emartin-kleppmann%E4%B8%8Eantirez%E7%9A%84%E8%AE%BA%E6%88%98%E8%AF%B4%E8%B5%B7/</guid>
      <description>从2016年Martin Kleppmann与antirez关于Redlock算法的论战出发，深度剖析分布式锁的设计困境。基于Redis官方文档、ZooKeeper Recipes、Jepsen测试报告、Google Chubby论文等权威信源，揭示分布式锁的本质：它不是互斥锁，而是租约。详细分析Redlock算法的时钟同步问题、GC暂停导致的安全漏洞，以及ZooKeeper/etcd如何通过临时顺序节点和Revision实现更安全的锁机制。重点解读Fencing Token的设计原理，以及为什么Jepsen发现etcd锁也会出现互斥违反。最后给出工程实践建议：效率优先选Redis单实例，正确性优先选共识系统。</description>
    </item>
    <item>
      <title>虚假唤醒：为什么条件变量会&#34;无缘无故&#34;地返回</title>
      <link>https://answer.freetools.me/%E8%99%9A%E5%81%87%E5%94%A4%E9%86%92%E4%B8%BA%E4%BB%80%E4%B9%88%E6%9D%A1%E4%BB%B6%E5%8F%98%E9%87%8F%E4%BC%9A%E6%97%A0%E7%BC%98%E6%97%A0%E6%95%85%E5%9C%B0%E8%BF%94%E5%9B%9E/</link>
      <pubDate>Fri, 06 Mar 2026 02:12:07 +0800</pubDate>
      <guid>https://answer.freetools.me/%E8%99%9A%E5%81%87%E5%94%A4%E9%86%92%E4%B8%BA%E4%BB%80%E4%B9%88%E6%9D%A1%E4%BB%B6%E5%8F%98%E9%87%8F%E4%BC%9A%E6%97%A0%E7%BC%98%E6%97%A0%E6%95%85%E5%9C%B0%E8%BF%94%E5%9B%9E/</guid>
      <description>深入解析虚假唤醒（Spurious Wakeup）的设计哲学与技术根源。从1974年Hoare的Monitor论文到Mesa语义的确立，揭示条件变量为何允许虚假唤醒、POSIX/Java/Windows等不同平台的处理方式，以及glibc/Linux内核的实现细节。这是一个被误解最深但设计最精巧的并发编程概念。</description>
    </item>
  </channel>
</rss>
