A system becomes a service through scheduling, identities, environments, observability and support. A fast benchmark cannot show whether researchers can reproduce and complete their jobs.
Define allocation rules, software ownership, support windows and recovery responsibilities. Report queue time, failures and useful completed work alongside hardware utilization.
Evidence to bring
- Scheduler and allocation policy
- Software environment and provenance
- Monitoring, incident and recovery ownership
Record the test conditions and the person responsible for validating the result. Resolve the largest uncertainty before treating this as a deployable design.
PRIMARY SOURCES · CHECKED 9 NOVEMBER 2026
Dell: Validated Design for Government →2026-10-19 · Reference design applies to described versions and configurations; assess current applicability.
NERSC: job best practices →Living documentation; checked 2026-11-09 · Facility-specific operational guidance; use local site policies for actual jobs.