diff options
Diffstat (limited to 'test/pdf_scroll_bench.zig')
| -rw-r--r-- | test/pdf_scroll_bench.zig | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/test/pdf_scroll_bench.zig b/test/pdf_scroll_bench.zig index 0f93068d..f3d47b1e 100644 --- a/test/pdf_scroll_bench.zig +++ b/test/pdf_scroll_bench.zig @@ -21,7 +21,7 @@ //! the single render — not on one notch. Every timed region below is exactly //! that: `ticks_per_frame` real `Mouse.wheel_down`/`wheel_up` presses through //! `Pardes.update`, one `render()` into a reset frame arena, and the effect -//! drain, which is the loop src/tty/tty.zig and src/gui/gui.zig both run. +//! drain, which is the loop src/tui/tui.zig and src/gui/gui.zig both run. //! //! Rows are per-FRAME latency, not per-notch: a dropped frame is what a reader //! feels, and the batch is indivisible from the reader's point of view. @@ -60,7 +60,7 @@ const gpa = std.heap.smp_allocator; // A reading-sized window. Wide enough that fit-width pages are taller than the // viewport (so a fling genuinely crosses page boundaries) and small enough // that the Kitty raster policy's 1200px cap is the binding quality term, which -// is what the tty shell actually ships. +// is what the tui shell actually ships. const bench_cols: u16 = 120; const bench_rows: u16 = 40; const default_cell_pixels: pardes.CellPixels = .{ .w = 8, .h = 16 }; @@ -383,7 +383,7 @@ fn measure(config: Config, plan: Plan) !Result { total += elapsed; recorder.observe(frame, surface); peak_raster_bytes = @max(peak_raster_bytes, rasterBytes(pv)); - // The same frame boundary src/tty/tty.zig marks, so a Tracy capture + // The same frame boundary src/tui/tui.zig marks, so a Tracy capture // of this benchmark reads like a capture of the real shell. pardes.frameMark(); if (round >= config.warmup) { |
