Terminal Phase 0: benchmark harness and baseline matrix (macOS reference + Windows)

Abierto
#239 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust

Línea de trabajo

Start with discussion #237 for the design rationale, then read the Roadmap section of docs/terminal.md where the proposed targets live. The deliverable is a harness plus committed baselines under docs/perf/, one run per machine entry in the matrix, each recording machine, build and driver. The DCS/APC/sixel byte-exact probe follows the noctty vt-conformance template, and the Windows side must cover both the inbox and bundled conpty.dll/OpenConsole.exe. This spans many machines and platforms, so it needs a maintainer to scope the first slice before anyone starts.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area: terminal priority: 1 high status: confirmed type: feature

Part of the native GPU terminal roadmap (milestone). Design and evidence: discussion #237.

Goal

Measure before building. Every later phase is judged against these numbers.

Scope

  • One harness on every platform: throughput (cat 100 MB ASCII, and the 10 MB 256-colour repaint burst + DSR from zed#61819), key→pixel latency, idle wakeups/s and GPU %, CPU with 4 agent TUIs at 30 redraws/s, RAM per terminal (10k and 1M lines), shell startup.
  • macOS baseline of today's native atlas-term (the parity reference; none is recorded yet).
  • Windows baseline of today's xterm.js path.
  • ConPTY probe: inbox vs bundled conpty.dll/OpenConsole.exe, byte-exact DCS/APC/sixel test (template: noctty vt-conformance).
  • GPU device cost per API. Spike already measured on Win11 Iris Xe: D3D11 32 MB / ~40 ms, D3D12 29 MB / ~50 ms, wgpu DX12 97 MB / ~115 ms.

Machine matrix

Win10 1809 (17763), 19045, LTSC 2019/2021; Win11 22631, 26100, 26200; Intel and AMD iGPU; VMware, Parallels, Hyper-V; an RDP session (D3D11 WARP).

Done when

Baselines committed under docs/perf/ with machine, build and driver per run; the proposed targets in docs/terminal.md (Roadmap) confirmed or adjusted.

Lenguaje dominante
Rust
Estrellas
3
Forks
1
Merge medio
9 h 51 min
PR fusionados (30 d)
310

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de codeatlasdev/atlas

Todos los issues de codeatlasdev/atlas

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.