| 6 Sep 2024 |
 zowoq |
the current aarch64 jobset only builds the variant for normal plug-in pcie GPUs not for jetson boards but we could extend it (which is probably the most common aarch64 user in fact...).
If jetson is the more common use case should we switch to building that instead of the current aarch64 jobset?
The jobset also only chooses the "fat" variants which include code for all available gpu architectures at once. We could spawn variants for individual architectures, which is particularly relevant for embedded systems.
If we built the individual architectures would we still need to build the fat variant? Is building an individual architecture quicker than the "fat" variant?
| 02:29:43 |
| zowoq | *
the current aarch64 jobset only builds the variant for normal plug-in pcie GPUs not for jetson boards but we could extend it (which is probably the most common aarch64 user in fact...).
If jetson is the more common use case should we switch to building that instead of the current aarch64 jobset?
The jobset also only chooses the "fat" variants which include code for all available gpu architectures at once. We could spawn variants for individual architectures, which is particularly relevant for embedded systems.
If we built the individual architectures would we still need to build the "fat" variant? Is building an individual architecture quicker than the "fat" variant?
| 02:29:58 |
 SomeoneSerge (matrix works sometimes) |
If jetson is the more common use case should we switch to building that instead of the current aarch64 jobset?
Imo yes | 02:33:46 |
 Jonas Chevalier |
I wonder what is the general idea for nix-community's sustainability?
The project is already sustainable, thanks to all of our donors <3
The main cost centre is hardware, which we scale depending on the amount of donations.
| 07:44:37 |
| Jonas Chevalier | One thing that could get more love is to add some reporting to the shared build boxes that people SSH into. Some MOTD that shows who else is on the box, and how many builds are currently running. | 07:49:43 |
| Jonas Chevalier | I imagine that people step over each other sometimes | 07:50:02 |
 emily | yeah I frequently have to do top to see if someone else is using it | 07:52:50 |
| Jonas Chevalier | would be cool if you could chat with the person if somebody is hogging the box | 07:56:31 |
| Jonas Chevalier | you can try echo hey, who is hogging the box? | wall on the machine, but not many people know you can do that | 07:57:20 |
 magic_rb | Unix has facilities for that | 07:57:21 |
| magic_rb | Exactly | 07:57:28 |
| Jonas Chevalier | I guess some instructions can be added to the MOTD as well | 07:58:07 |
| magic_rb | Or maybe we can symlink a markdown file into each of the users home dirs, like a manual thingie | 08:01:30 |
| emily | eh, my experience is that the builders are unused a large fraction of the time | 08:01:43 |
| magic_rb | (Mark the symlink readonly or smth so it cannot be gotten rid off) | 08:01:46 |
| emily | I don't mind people "hogging" it because I hog it at other times too :) | 08:01:50 |
| emily | though some kind of smart automatic scheduling could be cool | 08:02:04 |
| Jonas Chevalier | yes that would be real game changer. if we had good scheduling support, with priorities and resource accounting, we could also make the CI machines available, and reversely. But that's quite a bit of R&D | 08:24:59 |
| emily | it's not so bad to have to manually check in practice since often you need to baby-sit builds anyway | 08:26:29 |
| emily | (periodic "thanks for the builders, they make working on big Nixpkgs changes tolerable" :) ) | 08:26:40 |
| Jonas Chevalier | if we think crazy in the future, potentially, we could build every project on GitHub with a flake.nix | 08:32:39 |
| Jonas Chevalier | :p | 08:32:50 |
 nim65s | sounds like a job for slurm or similar | 08:41:54 |
| emily | In reply to @zimbatm:numtide.com
if we think crazy in the future, potentially, we could build every project on GitHub with a flake.nix yeah, like Nixpkgs! | 08:43:22 |
 Gaétan Lepage | Hi,
I have to admit that I often find myself heavily using the builders. Many of the packages I maintain are a pain to build and take a lot of resources. | 08:44:02 |
| Gaétan Lepage | Also, I very rarely explicitly SSH the builders and simply have them configured as remote-builders on my personal system.
Wouldn't messaging techniques like wall be inefective in this aspect ? | 08:45:04 |
| Gaétan Lepage | Maybe, there could be a matrix room with all the people that have been allowed to use the builder. What do you think ? | 08:45:58 |
| emily | I guess probably many people use them as remote builders. I don't because I'm paranoid and don't trust them | 08:47:39 |
| Jonas Chevalier | yeah good point. this is the matrix room | 08:47:42 |
| Jonas Chevalier | we should probably ask everybody to join this room | 08:48:04 |
