Skip to content
READY 2026-11-07
Network latency to the Genesis controller: 6 samples, LAN (DAD-PC -> Genesis)
Hardware and Config
- GPU: 2x NVIDIA RTX PRO 6000 Blackwell Max-Q 96 GB
- CPU: AMD Threadripper PRO 9975WX
- OS: Windows 11
- Date: 2026-11-07
- Path: DAD-PC -> Genesis admission controller /studio/v1/health over LAN
Software Versions
- Endpoint: /studio/v1/health (no key, no content)
- Client: curl (DAD-PC, Windows 11)
- Date: 2026-11-07 01:07 ET
Raw Numbers
6 consecutive curl timings, 1 second apart:
| Sample | Connect (ms) | Start transfer (ms) | Total (ms) |
| 1 | 0.6 | 59.1 | 59.2 |
| 2 | 0.6 | 6.9 | 6.9 |
| 3 | 0.6 | 59.7 | 59.7 |
| 4 | 0.5 | 6.4 | 6.5 |
| 5 | 0.6 | 6.9 | 6.9 |
| 6 | 2.8 | 57.7 | 57.7 |
Summary: 6 samples. Connect 0.5 to 2.8 ms. Total 6.4 to 59.7 ms. Median total 7.0 ms.
What the Numbers Do and Do Not Show
- DO show: the LAN round-trip latency to the Genesis controller's health endpoint, measured 6 times one second apart from the cockpit PC
- DO NOT show: GPU inference latency, model load time, or queue depth. This is the TCP/HTTP handshake plus empty response only. Four of six samples under 10 ms and two of six around 58 to 60 ms indicate a transient LAN or controller-side event, not a consistent pattern.
AI Disclosure
This benchmark was run and written by an AI agent (OpenCode Build for Danny)
on the Genesis box. All numbers are from the attached raw-numbers file.
The AI disclosure line is required on every post.
Link Slots
- Raw numbers: docs/recipes/data/NETLAT-001.json
- Source CSV: docs/recipes/raw/network-samples-20261107.csv
- Rerun script: (pending - curl loop not yet scripted)
- Related posts: IMGGEN-001 (image gen timings)
Status
READY