rsc-streaming-performance

What problem does it solve?

RSC streaming performance is often hindered by serial data fetches, poorly placed Suspense boundaries, and caching gaps that cause content to appear late and on error-prone cold starts.

Core Features & Use Cases

• Phase-based bottleneck diagnosis: read the page's server/component tree to identify serial awaits, waterfall data fetches, and caching gaps that slow rendering.
• Suspense decomposition patterns: split slow components into a sync shell and an async subtree wrapped in Suspense to stream content progressively.
• Redis cross-instance caching guidance: recommend rememberJson usage and proper cache keys to reduce bimodal latency while avoiding stale data.
• Use Case: On a production Next.js App Router page with multiple independent data fetches, apply this skill to reduce p95 latency and improve first contentful paint.

Quick Start

Audit a slow page by mapping the server component tree, identify serial awaits, and implement parallel data fetches with Suspense boundaries.