OpenParable
Skip to content
← Back to skills

Rezi Perf Profiling

Testing & Quality
rezi-perf-profiling

Rezi Perf Profiling is an Agent Skill for testing & quality published in the RtlZeroMemory/Rezi repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Profile and optimize Rezi app performance. Use when app feels slow, frames drop, or render phases take too long.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/RtlZeroMemory/Rezi/blob/HEAD/.codex/skills/rezi-perf-profiling/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/rezi-perf-profiling, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

When to use

Use this skill when:

  • App feels slow or unresponsive
  • Frames drop or input lags
  • Need to identify which render phase is the bottleneck
  • Optimizing a specific widget or screen

Source of truth

  • packages/core/src/app/widgetRenderer.ts — render pipeline with phase timing
  • packages/core/src/runtime/commit.ts — reconciliation (leaf/container reuse)
  • packages/core/src/layout/ — layout engine (FNV-1a stability signatures)
  • packages/core/src/widgets/composition.ts — animation utility hooks
  • packages/bench/src/ — profiling scripts

Steps

  1. Enable profiling and run:

    REZI_PERF=1 REZI_PERF_DETAIL=1 node your-app.js
    
  2. Observe phase timings: view → commit → layout → render → build

  3. Run systematic profiling:

    npx tsx packages/bench/src/profile-phases.ts
    npx tsx packages/bench/src/profile-construction.ts
    
  4. Apply common fixes:

    BottleneckFix
    View phase slowctx.useMemo(() => expensiveComputation, [deps]) for expensive computations
    Commit phase slowAdd key props on list items for stable reconciliation
    Layout phase slowReduce nesting depth; layout stability signatures skip relayout when tree is stable
    Render phase slowUse ui.virtualList() for large datasets
    Animation-heavy screen slowLimit transition scope (properties), animate only visible rows, avoid per-frame object churn
    Overall slowFlatten unnecessary wrapper nodes
  5. Depth guardrails:

    • Warning at 200 levels
    • Fatal at 500 levels
    • Refactor deep nesting into flatter structures

Key optimization patterns

  • ctx.useMemo(() => expensiveComputation, [deps]) — skip recomputation
  • key on every list item — enables O(1) reconciliation
  • ui.virtualList() — only renders visible rows
  • useStagger(...) + ui.virtualList(...) — stagger only the visible window
  • ui.box({ transition: { properties: [...] } }) — animate only required dimensions
  • Avoid creating new closures/objects in render — use ctx.useCallback(fn, [deps])