| 3 Apr 2026 |
hexa | but maybe we'll have to rethink how we do that | 16:31:23 |
hexa | it's currently 4 jobs/2cores on the M1 (8C, 16GB) and 2 jobs/4 cores big-parallel on the M2 (8C, 24G) | 16:32:41 |
hexa | Redacted or Malformed Event | 16:32:58 |
hexa | so, who can tell when m5 mini will be released? :p | 16:34:17 |
hexa | Redacted or Malformed Event | 16:34:24 |
samasaur | some rumors claim later this year, but based on what we've heard so far I wouldn't yet expect that with confidence | 16:39:43 |
hexa |  Download | 16:45:13 |
hexa | this is a rough summary of what models/combinations we discussed | 16:45:45 |
Ihar Hrachyshka | my gut reaction is more cores / ram is better than more disk space, and more machines is better than a few (->6xMini), but I am hesitant to say that without confirming the latest useful disk space on a .5TB machine on a headless macos. (my macbook air has .5TB and I at times feel strain on my nix store / gc, but it's probably because I collect crap and random apps) | 17:04:42 |
samasaur | I'm not super familiar with the disk space issue but if disk space long term is not an issue as much as disk space during a build, I would lean towards the 6x 512GB Mac minis as well | 17:05:22 |
Ihar Hrachyshka | assuming these are just builders and everything is then pushed into actual cache, we shouldn't need to keep nix store crap for long. | 17:08:51 |
samasaur | that's my thought process as well | 17:10:33 |
samasaur | do we know how full the existing Macs get? | 17:10:36 |
hexa | right now we have 256GB on all the M1s and they are churning super hard | 17:53:21 |
hexa |  Download these are from today | 17:53:59 |
hexa | and if you've seen a build getting disrupted by a full disk on hydra … well | 17:54:16 |
hexa | -sh-3.2# df -h
Filesystem Size Used Avail Capacity iused ifree %iused Mounted on
/dev/disk3s3s1 228Gi 11Gi 20Gi 37% 453k 213M 0% /
devfs 204Ki 204Ki 0Bi 100% 706 0 100% /dev
/dev/disk3s6 228Gi 2.0Gi 20Gi 9% 2 213M 0% /System/Volumes/VM
/dev/disk3s4 228Gi 14Gi 20Gi 42% 5.4k 213M 0% /System/Volumes/Preboot
/dev/disk3s2 228Gi 59Mi 20Gi 1% 69 213M 0% /System/Volumes/Update
/dev/disk1s2 500Mi 6.0Mi 483Mi 2% 3 4.9M 0% /System/Volumes/xarts
/dev/disk1s1 500Mi 5.7Mi 483Mi 2% 30 4.9M 0% /System/Volumes/iSCPreboot
/dev/disk1s3 500Mi 916Ki 483Mi 1% 32 4.9M 0% /System/Volumes/Hardware
/dev/disk3s1 228Gi 95Gi 20Gi 83% 2.2M 213M 1% /System/Volumes/Data
map auto_home 0Bi 0Bi 0Bi 100% 0 0 - /System/Volumes/Data/home
/dev/disk3s7 228Gi 82Gi 20Gi 81% 4.7M 213M 2% /nix
/dev/disk4 512Mi 12Mi 500Mi 3% 4 4.3G 0% /private/var/run/agenix.d
| 17:54:47 |
hexa | an example machine | 17:54:58 |
hexa | gc = {
automatic = true;
interval = [
{
Minute = 15;
}
{
Minute = 45;
}
];
# ensure up to 100G free space every half hour
options = "--max-freed $(df -k /nix/store | awk 'NR==2 {available=$4; required=100*1024*1024; to_free=required-available; printf \"%.0d\", to_free*1024}')";
};
| 17:55:30 |
hexa | but they never free up to 100G | 17:55:42 |
hexa | ok, does anyone know how to clean /var/db/uuidtext | 18:13:32 |
hexa | which takes 65GB of disk space on this one builder | 18:13:38 |
hexa | this seems to be logging related | 18:13:46 |
Randy Eckenrode | https://eclecticlight.co/2017/10/10/inside-the-macos-log-logd-and-the-files-that-it-manages/ | 18:15:13 |
hexa | I have an urge to find -mtime -delete | 18:16:27 |
Ihar Hrachyshka | log erase [--all] [--ttl] ?
| 18:44:00 |
Ihar Hrachyshka | man log | 18:44:03 |
antifuchs | Speaking of disk space on Mac builders, is there a way to customize the linux-builder vm image size? I keep running out there after a few (too few) builds | 20:09:12 |
Ihar Hrachyshka | nix = {
linux-builder = {
enable = true;
config =
{
virtualisation = {
darwin-builder = {
diskSize = 80 * 1024;
memorySize = 12 * 1024;
};
cores = 8;
};
};
};
};
| 20:12:07 |
antifuchs | Ooooooh | 20:14:21 |