ci-build reaches ~700 MB and is rewritten every job, on the machine that is also the mac-local runner for both app repos, so indexing it lands in the merge path for everything. mds_stores and mdworker_shared sit at the top of CPU while no build process is near it, which is why the load looked unexplainable.
Measured, same from-scratch build twice:
peak load
mds trailing after build
output indexed
128
minutes
output excluded
12.5
stops
The marker is written by the job rather than committed, because the directory it belongs in is created by the build and removed between runs.
The stable caches outside the repo were excluded on the host itself (DerivedData, Android SDK, the runner's builds directory, Gradle home - 11 GB between them). Verified honoured with an mdimport probe.
Android gets the same treatment for its module build dirs.
`ci-build` reaches ~700 MB and is rewritten every job, on the machine that is also the mac-local runner for both app repos, so indexing it lands in the merge path for everything. `mds_stores` and `mdworker_shared` sit at the top of CPU while no build process is near it, which is why the load looked unexplainable.
**Measured, same from-scratch build twice:**
| | peak load | mds trailing after build |
| --- | --- | --- |
| output indexed | 128 | minutes |
| output excluded | 12.5 | stops |
The marker is written by the job rather than committed, because the directory it belongs in is created by the build and removed between runs.
The stable caches outside the repo were excluded on the host itself (DerivedData, Android SDK, the runner's builds directory, Gradle home - 11 GB between them). Verified honoured with an `mdimport` probe.
Android gets the same treatment for its module build dirs.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
paulhitt
(Migrated from gitlab.com)
merged commit 668bd48415 into main2026-09-11 14:12:15 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
ci-buildreaches ~700 MB and is rewritten every job, on the machine that is also the mac-local runner for both app repos, so indexing it lands in the merge path for everything.mds_storesandmdworker_sharedsit at the top of CPU while no build process is near it, which is why the load looked unexplainable.Measured, same from-scratch build twice:
The marker is written by the job rather than committed, because the directory it belongs in is created by the build and removed between runs.
The stable caches outside the repo were excluded on the host itself (DerivedData, Android SDK, the runner's builds directory, Gradle home - 11 GB between them). Verified honoured with an
mdimportprobe.Android gets the same treatment for its module build dirs.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com