| 26 Jan 2025 |
 emily | the box's load average is ~2× the number of cores so it's pretty overloaded right now. I was going to fire off builds to test fixes for Darwin stdenv for the next staging-next cycle (due in ~2 days), and to try and reproduce the treewide Rust FOD hash replacement and check for any Darwin-specific issues, but it's struggling even as it is | 21:24:09 |
| emily | might be good to lower cores/max-jobs though I don't know if it's already overloaded from other builds | 21:24:55 |
 Ihar Hrachyshka | emily: ok sorry, I'm obtuse :) you want me to hold off for now? that's fine, I can do something else. | 21:24:59 |
| emily | could you just try with lower cores/max-jobs settings maybe? | 21:25:21 |
| emily | the default is 10 cores + 10 jobs, which can mean up to ~100 threads on a 10-core processor | 21:25:39 |
| emily | the stdenv build will take hours anyway so it's not urgent, but I don't want to throw more jobs at an already overloaded machine | 21:26:08 |
| Ihar Hrachyshka | it's 1 job for me. how do I limit the cores? is there a universal recipe or I patch cmake files? | 21:26:25 |
| emily | it's --option cores and --option max-jobs in Nix (-j for short on the latter) | 21:28:41 |
| emily | that said there are like 6 Python processes using up a huge amount of CPU so if you're only building one package I'm not sure it's the problem :) | 21:29:21 |
| Ihar Hrachyshka | I think I know which package it is lol | 21:31:43 |
| Ihar Hrachyshka | jax pretty sure | 21:31:48 |
