<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
    <title>Fork - 标签 - William</title>
    <link>https://williamlfang.github.io/tags/fork/</link>
    <description>Fork - 标签 | William</description>
    <generator>Hugo -- gohugo.io</generator><language>zh-CN</language><lastBuildDate>Wed, 30 Sep 2026 12:00:00 &#43;0900</lastBuildDate><atom:link href="https://williamlfang.github.io/tags/fork/" rel="self" type="application/rss+xml" /><item>
  <title>Why my tmux was laggy: the status bar was forking a 1.2 GB server 24 times a second</title>
  <link>https://williamlfang.github.io/2026-09-30-tmux-status-bar-lag/</link>
  <pubDate>Wed, 30 Sep 2026 12:00:00 &#43;0900</pubDate>
  <author>william</author>
  <guid>https://williamlfang.github.io/2026-09-30-tmux-status-bar-lag/</guid>
  <description><![CDATA[<p>My tmux had started to feel sluggish. Nothing was broken, it just felt heavy.
It turned out the tmux server was using about a third of a CPU core all the time,
and nearly all of that went on the status bar. Part of the cost came from the
clock workaround in my
<a href="/2026-09-26-linux-timezone-clock-and-tmux/">previous post</a>.</p>
<p>This post covers how I tracked it down, including two wrong guesses, and the fix,
which brought the server from <strong>~35% CPU to ~4%</strong> without restarting it.</p>]]></description>
</item>
</channel>
</rss>
