Scan time on large applications: measured breakdown and remaining options
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Refactorización
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- playwright, typescript, vite
- Área
- performance, testing-qa
Línea de trabajo
Start by measuring how quickly a passing focus move arrives, then benchmark Vite server.warmup and parallel screen scans as described in the issue. Compare results on a quiet machine and account for the source attributes needed by overlay file and line hints. Done means the measurements support a decision on which scan-time option to adopt.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Measured on a real product UI (one screen, about 55 seconds)
| Phase | Share |
|---|---|
| Readiness wait while the app mounts about 2,000 dev-server modules | 37% |
| Seven focus-settle timeouts at 2.5 s proving menus do not steal focus | 32% |
| Whole-DOM fetch per accessibility lookup (separate issue) | 16% |
| Keyboard walks, axe, everything else | 15% |
The lab tunnel was not the bottleneck: API calls cost about 300 ms more than local and overlap with module loading.
On a small application one screen takes about 10 seconds warm. Editing the vite config triggers a one-time dependency re-optimization that doubles the next scan.
Options not taken, with reasons
- Shortening
SETTLE_SAMPLES_REQUIREDrecovers about 1 second but guards a real two-burst mount regression. - Shortening
FOCUS_SETTLE_TIMEOUT_MSrecovers 2.5 seconds per unfocused widget but there is no measurement of how quickly a passing focus move arrives; shortening blind turns slow but correct focus into false failures. Measure a passing case first. - Running screens in parallel shares one browser process and a DOM-stability poll, so contention lengthens the wait; likely a loss on a loaded laptop. Measure before adopting.
- A production build removes the module-graph cost but drops the JSX source attributes the overlay's file and line hints read.
- Vite
server.warmupfor the target application may cut the module-graph time while keeping source attributes; unmeasured.
Direction
Measure a passing focus move; measure server.warmup; measure parallel screens on a quiet machine; then decide.
- Lenguaje dominante
- TypeScript
- Estrellas
- 0
- Forks
- 0
- Merge medio
- 2 h 48 min
- PR fusionados (30 d)
- 8
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
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 usabl-dev/usabl
-
area: engine bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
-
Stop hook allows a stop on an unknown verdict, and the self-check prints IDLE for a null verdictAbiertoarea: assistants bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
area: engine bug security
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Overlay: browser context failures are counted per plugin, not per browser, and close is not sharedAbiertoarea: overlay bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
-
area: engine enhancement performance
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Todos los issues de usabl-dev/usabl
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
maniator/verticopolis#1303 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
components-web-app/docs#297 ·
-
listFeatures/getFeatureExamples never return Kotlin examples for Android or server Kotlin SDKsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
appwrite/mcp-for-docs#23 · 1 comentario ·
-
`@vanilla-extract/turbopack-plugin`: "getImageSize is not a function" with Next.js 16.4.x when a `.css.ts` file imports an imagePosiblemente ocupada @aevarOrigo la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
vanilla-extract-css/vanilla-extract#1799 · 1 comentario ·
-
native
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
prime-radiant-inc/evener#4839 ·
Los mantenedores suelen responder en 1 día