!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

483 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.151 Servers

Load older messages


SenderMessageTime
18 Jun 2026
@hexa:lossy.networkhexathanks a ton for you work!14:58:44
@hexa:lossy.networkhexathe really slow part is now uploading to s315:25:02
@hexa:lossy.networkhexa where the smallest outputs take minutes in "Receiving outputs" 15:25:24
@hexa:lossy.networkhexae.g. systemd services, or rendered text files15:25:37
@hexa:lossy.networkhexaso the next step that we're looking at it is to move ingestion to a new bucket in de-fra15:26:03
@hexa:lossy.networkhexaand reconfigure fastly to fallback to us-east1 only when it hits 404 on the de-fra bucket15:26:39
@hexa:lossy.networkhexade-fra because currently 100% of our build farm sits in Germany15:27:35
@hexa:lossy.networkhexa(I blame hetzner for that)15:28:19
@hexa:lossy.networkhexaRedacted or Malformed Event15:28:22
@joerg:thalheim.ioMic92i think compression also still might be not the fastest in this setup15:34:32
@hexa:lossy.networkhexadid anything relevant about the s3 connection change? like, did we have long-lived keep alive before and no we don't?15:34:48
@hexa:lossy.networkhexaoh, so receiving uploads is compression + upload15:34:57
@hexa:lossy.networkhexagod we need to split that up for better visibility15:35:09
@hexa:lossy.networkhexaRedacted or Malformed Event15:35:24
@k900:0upti.meK900 I assume it's streaming compression? 15:35:44
@hexa:lossy.networkhexazstd should still be plenty fast for very small files15:35:44
@hexa:lossy.networkhexahttps://hydra.nixos.org/build/33166702915:35:59
@hexa:lossy.networkhexa
Download
15:36:08
@hexa:lossy.networkhexae.g. activate is fairly small15:36:18
@k900:0upti.meK900But yeah uploads for small outputs look really bad now15:36:21
@k900:0upti.meK900Significantly worse than before15:36:30
@hexa:lossy.networkhexathe old queue runner could do unstable-small in 30 minutes with fewest rebuilds15:37:13
@hexa:lossy.networkhexaRedacted or Malformed Event15:37:21
@hexa:lossy.networkhexaas a comparison15:37:39
@k900:0upti.meK900How good is the otel instrumentation currently on the runner/workers?15:38:57
@k900:0upti.meK900It might be good to spin up a Tempo instance so we can have proper metrics for this15:39:17
@k900:0upti.meK900Should be fairly easy to do15:39:27
@joerg:thalheim.ioMic92You can't really stream zstd with s3 unfortunally because s3 wants to know the size up-front. In niks3 I solved this by having smallish multi-part upload. I just yesterday introduced something similar in queue-runner because before it was just buffering everything in memory.15:40:14
@joerg:thalheim.ioMic92But I can try to make the parts a bit smaller.15:40:40
@hexa:lossy.networkhexaI don't immediately see an option to set up an otel endpoint in the module15:46:17

Show newer messages


Back to Room ListRoom Version: 6