| 12 Nov 2025 |
 raitobezarius | noticing not hitting the cache is definitely an art that is hard to master | 17:41:59 |
 aloisw | (or just break in fish, for that matter, given that they apparently want bash very specifically instead of any POSIX shell, which fish diverges from somewhat) | 17:45:33 |
 just1602 | There's pepole who actually use drbd outside of ganeti users, which are like Tor and Wikimedia? 😅 | 18:31:51 |
| raitobezarius | don't joke about this | 18:32:25 |
| raitobezarius | DGNum runs a drbd cluster | 18:32:27 |
| raitobezarius | drbd is still a quite nice solution :D :D :D | 18:32:36 |
| just1602 | Oh, it's really great, I happen to manage VM on ganeti with some friends and it does aesome thing... but I learned a couple of weeks ago that the version in the kernel is a fork that isn't really maintained and is way way behind upstream.... which scares me a little bit. :( | 18:33:49 |
| just1602 | * There's people who actually use drbd outside of ganeti users, which are like Tor and Wikimedia? 😅 | 18:34:05 |
| aloisw | Actually they did write it, I just missed it on the first pass reading. | 19:30:26 |
| aloisw | ("Storing a value in an attribute set (or list) preserves its pointer equality even if the structure holding it is modified in some way (as long as the value we care about is left untouched).") | 19:30:44 |
 Winter | @ma27 am i blind, or does both n-e-j and l-e-j default workers to 1, despite otherwise being said in the readme? https://git.lix.systems/lix-project/lix/src/commit/3ad1af8a9883986eb95744e088eab15c752c339c/subprojects/nix-eval-jobs/src/eval-args.hh#L33 | 19:59:16 |
| Winter | i cannot find a singular place that nrWorkers is set | 19:59:26 |
 ma27 | looking at the code, I'm pretty sure that subprojects/nix-eval-jobs/src/eval-args.cc on main does | 20:00:31 |
| 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 |
