| 5 Mar 2026 |
 emily | ok, I'll merge it and we can see | 15:11:41 |
| emily | could also just be more jobs appearing constantly and Darwin being some multiplicative factor slower I suppose | 15:12:15 |
 Lun | is this a good excuse to pgo&bolt the stdenv clang | 15:18:13 |
| emily | nah, would be bad for reproducibility | 15:18:49 |
| Lun | f | 15:18:55 |
 hexa | i'm like 20% on board with reproducibility being a focus of the project | 15:19:17 |
| emily | stdenv being inherently non-reproducible is certainly not okay | 15:21:07 |
| emily | for leaf packages it's less concerning | 15:21:17 |
| hexa | fair | 15:21:41 |
| emily | would be nice if we had deterministic PGO | 15:22:47 |
| emily | but it's hard | 15:22:50 |
| Lun | is hand tuned small top % wins reviewer legible proftext viable or would leaving most things with no instrumentation make it pessimize a lot. | 15:28:14 |
| emily | no idea :) | 15:30:09 |
| emily | I do know there are concerns about compilers not being hardened against malicious profile data (so they're essentially load-bearing trusted blobs even if we made them fixed), but I assume making it human-auditable would address that concern | 15:30:55 |
| Lun | will have to test it some time and not while having breakfast in a hotel lobby ig | 15:31:38 |
|  Caturday Reed changed their display name from Steve Reed to Caturday Reed. | 15:35:28 |
| Caturday Reed changed their profile picture. | 15:35:32 |
 vcunat | No, I don't know. But I'm quite sure that removing x86_64-darwin will help extremely. | 15:36:34 |
| emily | yeah for sure. just wondering what else might have gone on to make things worse recently | 15:37:08 |
| emily | we did just land the eval warning for x86_64-darwin | 15:37:14 |
| emily | need to get back to my stack that rips it out for 26.05 soon | 15:37:25 |
| vcunat | Maybe the last couple of cycles were slower for darwin, but it seems so now even for staging-next-25.11 and this kind of changes weren't backported, right? | 15:37:46 |
| vcunat | * Maybe the last couple of cycles felt slower for darwin, but it seems so now even for staging-next-25.11 and this kind of changes weren't backported, right? | 15:37:56 |
| emily | the change hit 25.11 | 15:38:10 |
| emily | so it was already present at release, AIUI | 15:38:20 |
| vcunat | Oh, OK. | 15:38:20 |
| emily | so if 25.11 got slower and wasn't always slow then it's probably not that | 15:38:33 |
| emily | but if 25.11 was always slower than 25.05 it could be that | 15:38:39 |
| emily | (unless it's "got slower once the builders were updated to 25.11" 😅) | 15:39:23 |
| vcunat | October was quite a long ago. | 15:39:31 |
