skip to content
[readonly]

10 packages match "state-machine"

  • total 11
  • drwxr-xr-x-../
  • drwxr-xr-x-Oct 27 04:09@ajax/mesh-placer/# 0.1.0 One placed program's state machine across the cluster: placement changes coordinated by the leader, state handed over, frames shown on every machine
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-app/# 0.1.0 mesh-top's viewer state: one machine per meshd endpoint with the history rates come from, tabs, focus, prompts, and every key binding
  • drwxr-xr-x-Oct 27 04:09@ajax/mesh-place-compose/# 0.1.0 A placed program's state and frame parts moved through its view, and whole frames composed from parts that arrive from several machines
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-ui-programs/# 0.1.0 mesh-top's Programs tab: a program table per machine (kind, state, placement, rates, task-time quantiles, executor CPU and RSS, PTX hash), the selected program's view pane with a hexdump, the trace flame chart and the log
  • drwxr-xr-x-Oct 27 04:08@ajax/mesh-fleet-core/# 0.1.0 The fleet's election and commit state machine (Raft's rules with PreVote and CheckQuorum, no log; a pair has a fixed coordinator), sans-IO
  • drwxr-xr-x-Oct 27 04:27@ajax/mesh-place-mode/# 0.1.1 How a program is placed across the cluster: local, pinned to one machine, or split by an assignment of its parts (with the auto split), and each machine's role
  • drwxr-xr-x-Oct 27 04:09@ajax/mesh-place-spec/# 0.1.0 A program's placement regions from its manifest: the shared state, the frame number and the output split into parts
  • drwxr-xr-x-Oct 27 05:24@ajax/mesh-load-host/# 0.1.0 This machine's load sample: the OS readers (CPU, PSI, memory, disk, thermal), rates between samples, the machine region and the member summary
  • drwxr-xr-x-Oct 27 07:31@ajax/mesh-peer-relay/# 0.1.1 The fleet thread: links, the election and commit core, changes forwarded to the leader, the leader's policies and scheduler, migrations, lockstep groups and the published fleet state
  • drwxr-xr-x-Oct 27 04:27@ajax/mesh-exec-wasm/# 0.1.0 meshd's wasm executor (BACKEND_WASM): CPU programs as WebAssembly modules on lease lanes, behind the backend interface