The memory is measured after the agent reaches its control plane
CI / test (push) Successful in 9m5s
CI / test (push) Successful in 9m5s
Measuring it in the startup scan held every agent half a second or more before registering, which on a shared CI runner was past the failover tests' wait. Now it runs once a process, in the background, the first time it is asked for, and Heartbeat.mem_bandwidth_gbs carries it when known; the control plane keeps the last figure and a heartbeat without one leaves it. The agent's tests do not measure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
84444e71c8
commit
e70d6caa2f
6 files changed
+83
-8
No files matched your search
@@ -591,6 +591,11 @@ message Heartbeat {
|
||||
// is not handed out. Empty from an agent that does not measure it, or from
|
||||
// one that could not this time.
|
||||
repeated int32 gpu_foreign_memory_mb = 19;
|
||||
|
||||
// mem_bandwidth_gbs is how fast the node's memory reads, in GB/s, once
|
||||
// the agent has measured it — in the background after it starts, so a
|
||||
// registration usually has none yet. 0 means not measured.
|
||||
double mem_bandwidth_gbs = 20;
|
||||
}
|
||||
|
||||
// Provision is the software a node should have: which engines, at which
|
||||
|
||||
Reference in new issue
Block a user