| 2 Apr 2025 |
 Grimmauld (any/all) | my linux x86_64 jas 4 builds left running, i'll slow on arm | 20:53:10 |
 emily | looks like both x86 and AArch64 Linux are overloaded right now | 20:53:19 |
| Grimmauld (any/all) | currently going through this list all building manually: https://github.com/NixOS/nixpkgs/pull/395499
i'll slow down | 20:53:42 |
| emily | wish we had the Nix load-limit PR, could set it globally and the machines wouldn't get like this no matter how many jobs get run | 20:53:44 |
 Gaétan Lepage | That seems like a very useful feature indeed | 20:54:20 |
| emily | might want to bump the cores/jobs down a bit, looks like we have 2–3 people running builds right now :) | 20:54:24 |
 Ihar Hrachyshka | maybe it's me. I'd love to see some guidance as to how I should build stuff though. | 20:54:25 |
| Grimmauld (any/all) | the x86_64 one should really be fine though, it only has 1 job running from me at this point | 20:54:27 |
| Grimmauld (any/all) | 
Download image.png | 20:54:44 |
| emily | I'll do what I was going to do on the Darwin one since that one is idle 😅 | 20:54:49 |
| Grimmauld (any/all) | will slow on the aarch64 though | 20:54:50 |
| Grimmauld (any/all) | Sorry! | 20:55:08 |
| Gaétan Lepage | 
Download clipboard.png | 20:55:09 |
| emily | you want cores × jobs < nproc always although when multiple people are using them that pretty much has to be divided by that | 20:55:31 |
| Grimmauld (any/all) | when i started this work it was completely idle | 20:55:33 |
| emily | thankfully the AArch64 one has so many cores that you can probably just pick something conservative and still have it finish faster than anything else would :P | 20:55:45 |
| emily | no worries. it's hard to load balance | 20:55:56 |
| Ihar Hrachyshka | I do 1 job and 20 cores on aarch64 but it's pytorch... | 20:55:56 |
| emily | and sorry again to Gaétan Lepage for the dodgy grep :) | 20:56:04 |
| Gaétan Lepage | Ideally we would need a scheduler like SLURM for those shared systems | 20:56:07 |
| Grimmauld (any/all) | thats exactly why i am building all those packages on aarch64-linux, it just is the fastest builder | 20:56:13 |
| Gaétan Lepage | In reply to @emilazy:matrix.org
and sorry again to Gaétan Lepage for the dodgy grep :) Fair enough, I have been the culprit quite a few times in the past ! | 20:56:30 |
| Ihar Hrachyshka | yeah I was thinking it's weird that we have to pick numbers for whole nixpkgs-review run when it really depends on whether others need the machine... | 20:56:49 |
| Grimmauld (any/all) | (i also hjonstly didn't expect to be able to overload the darwin machine just feeding single build jobs by hand...) | 20:56:57 |
| Grimmauld (any/all) | * (i also honstly didn't expect to be able to overload the darwin machine just feeding single build jobs by hand...) | 20:57:02 |
| Grimmauld (any/all) | * (i also honstly didn't expect to be able to overload the aarch64-linux machine just feeding single build jobs by hand...) | 20:57:10 |
| emily | the default is jobs = cores = nproc | 20:57:20 |
| emily | so as soon as two builds with >80 parallelizable C compiles happen it blows up | 20:57:40 |
| emily | (and it'll try to do 80 builds if it can, so very easy to go over) | 20:57:51 |
| Gaétan Lepage | The current SotA for this kind of use is ver sub-optimal | 20:57:59 |
