skip to content
[readonly]

17 packages match "counters"

  • total 18
  • drwxr-xr-x-../
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-net-counters/# 0.1.0 meshd's live network counters: bytes and frames per peer link and kind, the control port's and the HTTP relay's
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-host-block/# 0.1.0 meshd's host status block (S_* fields) under one lock, with its uptime clock and the live network counters
  • drwxr-xr-x-Oct 27 04:12@ajax/mesh-top-net/# 0.1.0 Network rates from meshd's cumulative counters on meshd's own clock (links, NICs, ports), and their human formatting
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-rt-ctx/# 0.1.0 What a mesh program sees (Ctx): views, peer views, input queue, pipes, request window, exchange page, counters, ids
  • drwxr-xr-x-Oct 27 05:24@ajax/mesh-nic/# 0.1.0 Network interface counters: /proc/net/dev (or macOS's 64-bit if_data), wrap-safe totals, NIC records
  • drwxr-xr-x-Oct 27 03:27@ajax/mesh-worker-ctx/# 0.1.1 What a native worker's init and task see: mesh-rt's Ctx on a CPU thread (views with fault recording, peer views, the input queue, pipes, the request window, counters)
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-abi-view-http/# 0.1.0 programs/http's view: a GPU HTTP server's counters, load request and windows
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-abi-host-net/# 0.1.0 Network I/O counters: the NIC sample clock, the control port's and HTTP relay's bytes
  • drwxr-xr-x-Oct 27 01:45@ajax/mesh-abi-control-block/# 0.1.0 A program's control block (P_*): shutdown, run state, faults, the request window, worker words, counters
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-prog-hello/# 0.1.0 hello, the smallest mesh GPU program (task = arg * 3 + 7), as PTX from C
  • drwxr-xr-x-Oct 27 02:56@ajax/mesh-cpuuse/# 0.1.0 What the CPU executors cost per slot: CPU time, resident bytes and lanes or processes, metered per thread
  • drwxr-xr-x-Oct 27 05:24@ajax/mesh-load-share/# 0.1.0 The GPU share maths of the load sampler: node load record deltas, share, slices, gaps, and nearest-rank quantiles
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-prog-pipesink/# 0.1.0 pipesink, the pipe demo's checking sink as a native mesh worker: drains digests, verifies each sha256d, histograms latency
  • drwxr-xr-x-Oct 27 02:57@ajax/mesh-worker-node/# 0.1.0 mesh-rt's node loop on CPU threads: claim published tickets, run init or task, complete them with results, marks, node records and traces
  • drwxr-xr-x-Oct 27 03:26@ajax/mesh-rt-loop/# 0.1.0 The node loop of every mesh program's kernel: tickets from the slot's ring, completion, heartbeat, load records, shutdown
  • drwxr-xr-x-Oct 27 02:56@ajax/cuda-driver-fake/# 0.1.0 A simulated CUDA device behind the cuda-driver table: modules, globals, streams and launches whose kernels run as C functions on CPU threads, for testing without a GPU
  • drwxr-xr-x-Oct 27 05:23@ajax/mesh-http-relay/# 0.1.0 meshd's HTTP port: request heads relayed to the GPU http program, and the routes meshd answers itself (the views, infer, render)