<?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 BvBeJ的小站</title><link>https://www.bvbej.com/tags/%E5%B9%B6%E5%8F%91/</link><description>Recent content in 并发 on BvBeJ的小站</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Sun, 17 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.bvbej.com/tags/%E5%B9%B6%E5%8F%91/feed.xml" rel="self" type="application/rss+xml"/><item><title>Rust Channel 背压模式：有界队列与拒绝策略</title><link>https://www.bvbej.com/posts/rust-channel-backpressure-patterns/</link><pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-channel-backpressure-patterns/</guid><description>高负载下的可预测行为，比单次吞吐更重要</description></item><item><title>C++ 锁竞争分析：从火焰图到优化路径</title><link>https://www.bvbej.com/posts/cpp-lock-contention-profiling/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/cpp-lock-contention-profiling/</guid><description>先定位热点锁，再决定分片、读写锁还是无锁化</description></item><item><title>C++ 原子变量与伪共享：低延迟场景避坑</title><link>https://www.bvbej.com/posts/cpp-atomics-false-sharing/</link><pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/cpp-atomics-false-sharing/</guid><description>cache line 争用常常比锁本身更先成为瓶颈</description></item><item><title>C++ 线程池：Work Stealing 的收益与代价</title><link>https://www.bvbej.com/posts/cpp-thread-pool-work-stealing/</link><pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/cpp-thread-pool-work-stealing/</guid><description>任务分布不均时，偷取队列可以提升吞吐但会增加复杂度</description></item><item><title>Rust Async 的 Cancellation Safety：避免半提交状态</title><link>https://www.bvbej.com/posts/rust-async-cancellation-safety/</link><pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-async-cancellation-safety/</guid><description>取消并不等于回滚，未设计的中断会留下难排查的数据破坏。</description></item><item><title>Rust Tokio 取消安全：避免半完成状态</title><link>https://www.bvbej.com/posts/rust-tokio-cancellation-safety/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-tokio-cancellation-safety/</guid><description>异步任务可取消不等于安全可取消，关键是边界和幂等</description></item><item><title>Rust 无锁结构中的内存回收：Epoch 与 Hazard Pointer 对比</title><link>https://www.bvbej.com/posts/rust-lockfree-memory-reclamation/</link><pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-lockfree-memory-reclamation/</guid><description>无锁算法真正难点不是 CAS，而是安全回收被并发读取的节点。</description></item><item><title>Go Worker Pool：饱和控制与降级策略</title><link>https://www.bvbej.com/posts/go-worker-pool-saturation-control/</link><pubDate>Mon, 27 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-worker-pool-saturation-control/</guid><description>Worker Pool 不是为了并发更高，而是为了并发可控</description></item><item><title>Go Worker Pool 与背压：不靠拍脑袋定并发数</title><link>https://www.bvbej.com/posts/go-workerpool-backpressure-tuning/</link><pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-workerpool-backpressure-tuning/</guid><description>通过吞吐、延迟、队列深度三个指标，系统化调优 worker pool</description></item><item><title>Go Context 取消链路：别让 goroutine 泄漏</title><link>https://www.bvbej.com/posts/go-context-cancellation-patterns/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-context-cancellation-patterns/</guid><description>围绕 context 的传播、超时与取消，建立可维护的并发边界</description></item><item><title>C++ 无锁队列：从 CAS 到内存序</title><link>https://www.bvbej.com/posts/cpp-lockfree-queue-memory-order/</link><pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/cpp-lockfree-queue-memory-order/</guid><description>无锁结构不只是把 mutex 去掉，更关键的是搞清楚原子操作和内存序到底在保证什么</description></item><item><title>Rust Tokio 背压控制：异步系统别只会拼命 spawn</title><link>https://www.bvbej.com/posts/rust-tokio-backpressure/</link><pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-tokio-backpressure/</guid><description>异步不等于无限并发，背压设计决定了 Tokio 服务在高负载下是稳定还是失控</description></item><item><title>Go 并发模式：Pipeline 实战</title><link>https://www.bvbej.com/posts/go-concurrency-patterns/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/go-concurrency-patterns/</guid><description>聊聊 Go 中 Pipeline 的设计模式与最佳实践</description></item></channel></rss>