jschoubben
b712123f2b
It watches its node's keys of mesh-host_data instead of composing every module's items from about 370 resolved keys per round, so a round no longer takes 30 to 45 minutes across the tunnel and a manifest its mesh-sdk cannot judge no longer silences it. A changed key measures its module at once; each round writes how far it got to the per-node state rounds, said by disk_round. Pins mesh-sdk feat/data-items. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL
17 lines
684 B
Go
17 lines
684 B
Go
package main
|
|
|
|
// The readings layout, their key and the peak are mesh-sdk's (health.Reading, health.NextReading; novox/hq ADR 0571
|
|
// clause 3): disk-load measures each placed data item of its node and keeps the readings as its own state.
|
|
|
|
import "git.novox.be/novox/mesh-sdk/go/health"
|
|
|
|
// StateReadings is the state disk-load keeps.
|
|
const StateReadings = health.ReadingsState
|
|
|
|
// StateRounds is its state of each node's last round, key `<node>` (novox/hq ADR 0577 clause 3): apart from the readings,
|
|
// so a reader of the readings never meets a round.
|
|
const StateRounds = "rounds"
|
|
|
|
// ClassCache is the class of an item that is listed and never measured.
|
|
const ClassCache = "cache"
|