Warm pool: the refill boot after every lease grant takes half of a 10-core Mac for 90 s, and nothing paces it
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- ios, macos, typescript
- Área
- performance, tooling
Línea de trabajo
Start in the warm-pool converger that reacts to lease.granted: find where the replacement is cloned and booted, then the warmPool settings schema defining maxConcurrentBoots, memoryPressure and reserveRunning.ios, and the slim-mode category list that ties widgets to PosterBoard and chronod. Read #1540 for the seed-shutdown context, then reproduce with one warm target and maxConcurrentBoots: 1 while sampling host idle. Done means either a pacing control (a post-grant delay or a host-CPU gate) or an ios.slim wallpaper category, backed by tests.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
[!NOTE]
Claude Fable 5.2 responding on behalf of Melvin
The problem
On a Mac that runs builds beside a warm iOS pool, every lease grant is followed by about 90 seconds in which the host has no idle CPU. The cause is not the simulator that was just leased. It is the warm pool's refill: the converger runs on lease.granted, clones a seed and boots the copy at once, and that copy's first boot is the expensive part.
Measured on Simlock 0.7.0, iOS 27 runtime, a 10-core Apple silicon Mac, one warm iPhone 17 target, maxConcurrentBoots: 1, slim mode on without the widgets category. CPU is per-process CPU time sampled and grouped by each simulator's launchd_sim; host idle is from iostat.
One refill boot, from "replacement provisioned" (5 s after the grant) for 92 s. Host idle was 0% in every sample.
| Who | Core-seconds in 92 s |
|---|---|
| The replacement warm simulator (first boot) | 458 (5 of the 10 cores; 88% of all simulator CPU) |
| The simulator leased 5 s earlier | 30 |
| A simulator that was already leased | 32 |
| Host processes (a native build) | 264, down from 550 in the 87 s before (6.3 cores to 2.9) |
The replacement's 458 core-seconds by process class:
| Class | Core-seconds | Share |
|---|---|---|
| Poster extensions and PosterBoard (wallpapers) | 125 | 27% |
Widget extensions and chronod |
122 | 27% |
| Other daemons | 95 | 21% |
lsd, SpringBoard, launchd_sim |
55 | 12% |
diagnosticd, logd |
28 | 6% |
MTLCompilerService |
12 | 3% |
| Below the sampler's floor | 21 | 4% |
Load average on the same host, to separate the boot from the lessee's own work:
- Refill boot alone (the lessee did nothing yet): peaks of 154 and 176.
- Refill boot with the lessee starting its app inside the window: peaks of 197 and 199.
- A release with no new grant (so only the replacement boots): peak 293.
- A grant with no refill (pool at its capacity, so nothing booted): 26 to 65 over two minutes.
So the build beside the pool loses more than half of its CPU, and the lessee's first app start runs on a starved host, once per lease.
Nothing in 0.7.0's warmPool settings changes when or how hard that boot runs. maxConcurrentBoots is already 1. memoryPressure reads memory only, and memory is fine during the burst. reserveRunning.ios set to the target plus one moves the same boot to after the last release and makes every lease taken while another is held wait for a cold clone and boot (3.2 s and 20.9 s median here, 25.5 s p90).
The slim category that would remove most of it is widgets, which disables PosterBoard and chronod together. That is 54% of the burst, but an app under test that has home-screen widgets or a Live Activity needs chronod, so the category cannot be switched on for such a pool. The wallpaper half (27%) has no category of its own.
Who runs into this
Coding agents and CI jobs sharing one Mac: agents lease simulators from a warm pool while native builds and a CI pool run on the same host. Leases come in steadily (37 grants in one day here), so the host spends a noticeable part of the day in these windows, and callers that gate on host load before starting work see the pool itself trip the gate.
What you would like to happen
Two things, either of which helps without the other:
- A way to pace the refill. For example a
warmPooldelay afterlease.grantedbefore the replacement boots, or a host CPU gate beside the memory one that holds warming (without shedding idle devices) while the host is saturated. A lease that arrives while the refill is held would be created on demand, as it is today when nothing is warm. - Wallpapers separable from widgets in slim mode: a category of its own for PosterBoard and the poster extensions, or
ios.slimaccepting launchd labels, so a pool can drop the wallpaper work and keepchronodand Live Activities.
Anything else
- Related: #1540 (the seed is shut down right after
bootstatus, so every clone repeats first-boot work). If seeds settled, this burst would probably shrink at the source; pacing the refill would still help hosts where a boot competes with a build. - Caveats on the numbers: the class split comes from one sampled boot, taken while a build ran beside it, and processes that start and exit between samples are not counted. The load peaks come from five separate grants and releases on the same day.
- No workaround is in use today; the settings above were weighed and left unset for the reasons given.
- Lenguaje dominante
- TypeScript
- Estrellas
- 705
- Forks
- 40
- Merge medio
- 12 h 9 min
- PR fusionados (30 d)
- 376
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de callstackincubator/simlock
-
request:new
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
callstackincubator/simlock#1806 ·
Los mantenedores suelen responder en 1 día
-
bug:new
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
callstackincubator/simlock#1780 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
task:draft
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
callstackincubator/simlock#1441 ·
Los mantenedores suelen responder en 1 día
-
bug:new
Dificultad 2/5 1-3 horas Aptitud para principiantes 45/100
callstackincubator/simlock#1805 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug:new
Dificultad 2/5 1-3 horas Aptitud para principiantes 45/100
callstackincubator/simlock#1804 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de callstackincubator/simlock
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
Update project links after the repository renamesPosiblemente ocupada @JonathanTSilva la tomó hoy. Abiertoai-generated priority: p2 size: xs type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
JonathanTSilva/jts-website#119 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
promplate/code-review#158 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
[Docs] CONTRIBUTING points the Backend Remake milestone at a branch that does not existPosiblemente ocupada @franpts2 la tomó hoy. Abiertodocs
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
Los mantenedores suelen responder en 3 días