<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>缓存 on 黄文卓 | DevOps Engineer</title>
    <link>https://socake.github.io/tags/%E7%BC%93%E5%AD%98/</link>
    <description>Recent content in 缓存 on 黄文卓 | DevOps Engineer</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>zh-CN</language>
    <managingEditor>17691281867@163.com (Wenzhuo Huang)</managingEditor>
    <webMaster>17691281867@163.com (Wenzhuo Huang)</webMaster>
    <copyright>© 2026 Wenzhuo Huang</copyright>
    <lastBuildDate>Sat, 03 Jan 2026 10:00:00 +0800</lastBuildDate><atom:link href="https://socake.github.io/tags/%E7%BC%93%E5%AD%98/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>BuildKit 缓存生产实战：从多阶段到远端 Registry Cache</title>
      <link>https://socake.github.io/posts/buildkit-cache-production/</link>
      <pubDate>Sat, 03 Jan 2026 10:00:00 +0800</pubDate>
      <author>17691281867@163.com (Wenzhuo Huang)</author>
      <guid>https://socake.github.io/posts/buildkit-cache-production/</guid>
      <description>BuildKit 的缓存体系看似简单一行 &amp;ndash;cache-to，实际生产里坑极多：mode=max 在多架构下的 manifest 行为、registry 后端每层 0.3s 的验证开销、cache mount 在 &amp;ndash;cache-to=registry 下不被导出的限制、GHA 后端 10GB 上限……本文基于真实 CI 流水线的调优记录，给出一套可复制的生产配置。</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/posts/buildkit-cache-production/featured.jpg" />
    </item>
    
    <item>
      <title>Redis 运维实践：持久化配置、集群模式与生产监控</title>
      <link>https://socake.github.io/posts/redis-ops-practice/</link>
      <pubDate>Wed, 06 Nov 2024 10:20:00 +0800</pubDate>
      <author>17691281867@163.com (Wenzhuo Huang)</author>
      <guid>https://socake.github.io/posts/redis-ops-practice/</guid>
      <description>Redis 运维看起来简单，但真到了生产出了问题才知道水有多深。本文整理了持久化、集群、监控、故障处理等核心运维主题。</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/posts/redis-ops-practice/featured.jpg" />
    </item>
    
  </channel>
</rss>
