| 12 Nov 2025 |
 ma27 | (only speaking for lix here, but n-e-j does probably the same, that's no change from us iirc) | 20:00:45 |
 Winter | i don't see this at all? | 20:01:33 |
| Winter | i only see a handler for going from passed arg -> int | 20:01:40 |
| ma27 | blargh good evening I misread the question | 20:02:20 |
| ma27 | apologies | 20:02:26 |
| ma27 | one sec | 20:02:27 |
| Winter | :-) | 20:02:36 |
| Winter | yeah setting --workers [n>1] makes this speed along | 20:03:09 |
| Winter | and i actually see 4 workers being spawned | 20:03:19 |
| Winter | and my memory+cpu being hammered | 20:03:29 |
| Winter | 😉 | 20:03:34 |
| ma27 | but, what are you referring to in the readme? afaiu it doesn't say something else (or rather, nothing on the default), no? | 20:06:53 |
| Winter | By default, nix-eval-jobs spawns as many worker processes as there are hardware threads in the system and limits the memory usage for each worker to 4GB.
| 20:07:22 |
| Winter | By default, nix-eval-jobs spawns as many worker processes as there are hardware threads in the system and limits the memory usage for each worker to 4GB.
| 20:07:30 |
| ma27 | ah right. | 20:08:51 |
| ma27 | yeah no you're right. | 20:09:17 |
| ma27 | feel free to file a cl :) | 20:09:21 |
