!eWOErHSaiddIbsUNsJ:nixos.org

NixOS CUDA

308 Members
CUDA packages maintenance and support in nixpkgs | https://github.com/orgs/NixOS/projects/27/ | https://nixos.org/manual/nixpkgs/unstable/#cuda59 Servers

Load older messages


SenderMessageTime
16 Apr 2026
@hexa:lossy.networkhexa (UTC+1)https://hydra.nixos-cuda.org/jobset/nixos-cuda/cuda-packages-unstable#tabs-evaluations13:35:18
@hexa:lossy.networkhexa (UTC+1)the last eval was two weeks ago13:35:24
@sporeray:matrix.orgRobbie Buxton
In reply to @hexa:lossy.network
that seems unlikely
Idk I’ve oomed on packages with over 1TB of ram
13:36:51
@hexa:lossy.networkhexa (UTC+1)wat\13:37:01
@hexa:lossy.networkhexa (UTC+1)Redacted or Malformed Event13:37:03
@gsaurel:laas.frnim65sbut you build with how many cores?13:37:23
@hexa:lossy.networkhexa (UTC+1)a) you can run out of ram with exccessive cores13:37:29
@gsaurel:laas.frnim65s* but you build with how many cores ?13:37:31
@hexa:lossy.networkhexa (UTC+1)b) without excessive cores the most ram usage is during linking13:37:38
@hexa:lossy.networkhexa (UTC+1)I'd say firefox takes at most 40 GB to link13:37:55
@sporeray:matrix.orgRobbie Buxton I was using nixbuild.net and it kept sizing it up and giving it more cores, and yeah the solution was reducing cores obviously 13:38:02
@hexa:lossy.networkhexa (UTC+1)that's not friendly at all, but does fit on my desktop still13:38:12
@hexa:lossy.networkhexa (UTC+1)but that means your core/ram balance was way off13:38:28
@sporeray:matrix.orgRobbie Buxton
In reply to @hexa:lossy.network
but that means your core/ram balance was way off
How so?
13:39:20
@hexa:lossy.networkhexa (UTC+1)you have a base need of RAM per core13:39:51
@hexa:lossy.networkhexa (UTC+1)just to run the build on it13:39:58
@hexa:lossy.networkhexa (UTC+1)and if you oom the total cores probably needed more ram than what was provided13:40:17
@hexa:lossy.networkhexa (UTC+1)and the solution would have been to get fewer cores with more ram instead13:40:30
@sporeray:matrix.orgRobbie BuxtonIdk I can’t get more than 1.6 TB of ram on AWS 😁13:40:42
@hexa:lossy.networkhexa (UTC+1)now I don't know anything about how nixbuild.net does scaling13:40:56
@sporeray:matrix.orgRobbie Buxton The large instances have interesting ratios 13:40:55
@hexa:lossy.networkhexa (UTC+1)yeah, but if you get 10k cores at the same time, then what?13:41:09
@sporeray:matrix.orgRobbie Buxton Iirc it’s not that smart for sizing (the service itself is fab tho) 13:41:32
@hexa:lossy.networkhexa (UTC+1)that's 160 MB per core if I didn't miscalculate13:41:38
@sporeray:matrix.orgRobbie Buxton
In reply to @hexa:lossy.network
yeah, but if you get 10k cores at the same time, then what?
On a single machine I can dream
13:41:47
@hexa:lossy.networkhexa (UTC+1)right13:41:55
@glepage:matrix.orgGaétan Lepage Yes, our cuda-packages jobset is broken because python3Packages.deep-ep emits a warning at eval time. 13:56:06
@glepage:matrix.orgGaétan Lepage If someone may review https://github.com/NixOS/nixpkgs/pull/510375, we could start building again 13:56:23
@glepage:matrix.orgGaétan LepageSorry everyone for the disruption13:56:35
@ss:someonex.netSomeoneSerge (matrix works sometimes)A reminder that the cache is not an officially maintained cuda team thing at the moment, and only exposed as an accidental dev artifact. Reminder that "stable channels" are not an official cuda team thing. Only hydra itself is. For the time being.14:00:03

There are no newer messages yet.


Back to Room ListRoom Version: 9