Hydra | 387 Members | |
| 111 Servers |
| Sender | Message | Time |
|---|---|---|
| 10 Apr 2023 | ||
| So only merging into a single multi-output derivation would help (but with other drawbacks, of course) | 14:10:57 | |
| Yes | 14:12:02 | |
| But we don't want to do that | 14:12:05 | |
| It's not like we're hitting any real limit | 14:12:18 | |
| It's mostly just that the queue runner is old and janky and not very fast | 14:12:39 | |
| But it could be made a lot faster | 14:12:44 | |
| With large number of jobs, I suspect the cost (apart from evaluation) is about S3 queries on all output paths across Atlantic (and serialized, I suspect) and then potentially moving lots of data to/from builders. | 14:15:57 | |
| * With large number of jobs, I suspect the cost (apart from evaluation) is about S3 queries on all output paths across Atlantic (and serialized, I suspect) and then potentially moving lots of data to/from builders (some of which could again be relatively far). | 14:16:59 | |
| That's for hydra.nixos.org in particular. Normally you'd probably try putting all the machines close together... | 14:18:36 | |
| 11 Apr 2023 | ||
| 16:06:44 | ||
| 12 Apr 2023 | ||
| 09:09:28 | ||
| 14 Apr 2023 | ||
| Have I to do something in particular in order to make remote builder for a different
I've this on my machine ( Am I missing something? | 07:54:27 | |
PS: I'm using hydra from a pretty recent nixos-untable updated days/weeks ago | 07:56:36 | |
| Logs don't help, if I manually restart the build from the UI I get this:
| 07:58:10 | |
I don't really know these things, but I'd look if this appears right: /admin/machines | 08:01:05 | |
* I don't really know these things, but I'd look if this appears right: http://*/admin/machines | 08:01:20 | |