!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

377 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.114 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
21 Aug 2025
@k900:0upti.meK900 (and probably should be done outside official infra, at least initially) 15:46:06
@vcunat:matrix.orgvcunatTrust is needed. People who have physical access to the HW can more-or-less put anything into the cache.15:53:05
@vcunat:matrix.orgvcunat(though not trivially at least)15:53:34
@rosscomputerguy:matrix.orgTristan RossIf the infra team doesn't have physical access but the hardware team does, is that acceptable for trust?15:53:55
@k900:0upti.meK900 Would not be great 15:54:38
@k900:0upti.meK900But also, again, I want to first see proof that there's enough hardware15:54:38
@k900:0upti.meK900 And that there's enough demand to justify the Hydra costs 15:54:43
@rosscomputerguy:matrix.orgTristan RossWhat sort of costs does it make on Hydra? Is it just eval and storage?15:55:56
@k900:0upti.meK900 Queue runner is slow 15:56:35
@emilazy:matrix.orgemilycache for the entire jobset on a new platform is substantial (since we pay the whole cost every staging cycle)15:56:40
@k900:0upti.meK900 Queue runner slowness scales with number of jobs 15:56:44
@emilazy:matrix.orgemilyand Hydra scheduling is a bottleneck15:56:53
@k900:0upti.meK900 Storage is also still questionable 15:56:59
@k900:0upti.meK900 Eval is largely not an issue 15:57:06
@emilazy:matrix.orgemilyI think it would make sense to prove this externally first15:57:12
@emilazy:matrix.orgemilywith a separate Hydra15:57:23
@emilazy:matrix.orgemilyand see if the hardware can even keep up15:57:33

Show newer messages


Back to Room ListRoom Version: 6