Streaming long operations in NextJS - Performance & Optimization

Performance: Streaming long operations

HIGH IMPACT

This affects how quickly users see content during long server operations by sending partial data progressively.

Rendering a page with a long server-side operation

NextJS

import React from 'react';

export default async function Page() {
  const stream = fetchLongDataStream();
  return (
    <div>
      <React.Suspense fallback={<Loading />}>
        <StreamingContent stream={stream} />
      </React.Suspense>
    </div>
  );
}

Streams data progressively to the client, allowing partial content to render early and improve perceived speed.

📈 Performance GainReduces LCP by showing content chunks as they arrive, improving user experience during long operations

Rendering a page with a long server-side operation

NextJS

export default async function Page() {
  const data = await fetchLongData();
  return <div>{data}</div>;
}

The entire data must load before rendering, blocking the first paint and delaying user feedback.

📉 Performance CostBlocks rendering until data fetch completes, increasing LCP by several seconds for long operations

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Blocking full data fetch	Single large DOM update after full data	1 reflow after full data	High paint cost due to large update	[X] Bad
Streaming partial content	Multiple small DOM updates progressively	Multiple small reflows but faster perceived paint	Lower paint cost per chunk	[OK] Good

Rendering Pipeline

Streaming sends partial HTML chunks progressively, allowing the browser to start parsing and painting before the full content is ready.

→Network

→HTML Parsing

→Paint

→Composite

⚠️ BottleneckNetwork and HTML Parsing waiting for full data in non-streaming; streaming reduces this wait.

Core Web Vital Affected

LCP

This affects how quickly users see content during long server operations by sending partial data progressively.

Optimization Tips

1Stream partial HTML to reduce time before first meaningful paint.

2Use React Suspense to handle loading states during streaming.

3Balance chunk size to avoid too many small reflows while keeping content progressive.

Performance Quiz - 3 Questions

What is the main performance benefit of streaming long operations in Next.js?

A It allows partial content to render early, improving perceived load speed.

B It reduces the total amount of data sent over the network.

C It eliminates the need for server-side rendering.

D It caches all data on the client to avoid future requests.

DevTools: Performance

How to check: Record a page load with streaming enabled, look for early Contentful Paint and progressive HTML parsing in the flame chart.

What to look for: Early LCP event and incremental DOM updates showing partial content rendering before full data arrives.

Practice

1. What is the main benefit of using streaming in Next.js for long operations?

easy

A. Users see data progressively, reducing perceived wait time.

B. It automatically caches all data on the server.

C. It compresses data to reduce bandwidth usage.

D. It prevents any errors during data fetching.

Solution

1. Step 1: Understand streaming purpose

   Streaming sends data in chunks so users can see progress during long operations.

2. Step 2: Identify user experience impact

   This reduces the perceived wait time by showing partial results early.

3. Final Answer:

   Users see data progressively, reducing perceived wait time. -> Option A

4. Quick Check:

   Streaming improves user experience = A [OK]

Hint: Streaming shows partial data early to users [OK]

Common Mistakes:

• Thinking streaming caches data automatically
• Confusing streaming with data compression
• Assuming streaming prevents all errors

2. Which syntax correctly creates a streaming response in a Next.js API route?

easy

A. const stream = new ReadableStream({ start(controller) { controller.enqueue('data'); controller.close(); } }); return new Response(stream);

B. const stream = new StreamReader(); stream.push('data'); return stream;

C. const stream = new WritableStream(); stream.write('data'); return stream;

D. const stream = new ReadableStream(); stream.send('data'); return stream;

Solution

1. Step 1: Recall correct ReadableStream usage

   ReadableStream requires a start method with a controller to enqueue data and close the stream.

2. Step 2: Match syntax with Next.js streaming pattern

   const stream = new ReadableStream({ start(controller) { controller.enqueue('data'); controller.close(); } }); return new Response(stream); uses controller.enqueue and controller.close correctly and returns a Response wrapping the stream.

3. Final Answer:

   const stream = new ReadableStream({ start(controller) { controller.enqueue('data'); controller.close(); } }); return new Response(stream); -> Option A

4. Quick Check:

   ReadableStream with controller.enqueue = B [OK]

Hint: Use ReadableStream with start(controller) and enqueue [OK]

Common Mistakes:

• Using WritableStream instead of ReadableStream
• Calling non-existent methods like send() or push()
• Not closing the stream after enqueue

3. Given this Next.js API route code, what will the client receive?

export async function GET() {
  const stream = new ReadableStream({
    async start(controller) {
      controller.enqueue(new TextEncoder().encode('Hello '));
      await new Promise(r => setTimeout(r, 1000));
      controller.enqueue(new TextEncoder().encode('World!'));
      controller.close();
    }
  });
  return new Response(stream);
}

medium

A. Only "Hello " is received; stream never closes.

B. "Hello World!" received in two chunks with 1 second delay between.

C. "Hello World!" received all at once after 1 second delay.

D. Syntax error due to missing await in controller.enqueue.

Solution

1. Step 1: Analyze streaming behavior

   The stream first sends "Hello " immediately, then waits 1 second before sending "World!".

2. Step 2: Understand client reception

   The client receives data in two chunks with a delay, then the stream closes properly.

3. Final Answer:

   "Hello World!" received in two chunks with 1 second delay between. -> Option B

4. Quick Check:

   Streaming sends chunks with delay = C [OK]

Hint: Streaming sends chunks as they enqueue, not all at once [OK]

Common Mistakes:

• Assuming all data arrives after delay
• Thinking stream never closes
• Confusing async enqueue with syntax error

4. What is wrong with this Next.js streaming code snippet?

export async function GET() {
  const stream = new ReadableStream({
    start(controller) {
      controller.enqueue('Data chunk');
      // Missing controller.close()
    }
  });
  return new Response(stream);
}

medium

A. ReadableStream cannot be used in Next.js API routes.

B. controller.enqueue must be async function.

C. The stream never closes, causing the client to wait indefinitely.

D. Response must be wrapped in JSON.stringify.

Solution

1. Step 1: Check stream lifecycle

   The code enqueues data but does not call controller.close(), so the stream stays open.

2. Step 2: Understand client impact

   The client waits forever for the stream to end, causing a hang or timeout.

3. Final Answer:

   The stream never closes, causing the client to wait indefinitely. -> Option C

4. Quick Check:

   Missing controller.close() = stream hangs [OK]

Hint: Always call controller.close() after enqueueing all data [OK]

Common Mistakes:

• Forgetting to close the stream
• Thinking enqueue must be async
• Misunderstanding Response usage

5. You want to stream a large list of items from a Next.js API route, sending each item as JSON chunk. Which approach correctly streams the data without blocking the client?

hard

A. Send each item with separate fetch requests instead of streaming.

B. Convert entire list to JSON string, enqueue once, then close the stream.

C. Use WritableStream to write each JSON chunk and return it directly.

D. Use ReadableStream with async start(controller), loop over items, enqueue JSON strings, and close after all.

Solution

1. Step 1: Understand streaming large data

   Streaming each item as JSON chunk progressively sends data without waiting for all items.

2. Step 2: Identify correct streaming pattern

   Using ReadableStream with async start allows looping over items, enqueueing each chunk, then closing the stream.

3. Step 3: Evaluate other options

   A requires multiple requests (inefficient); B sends all data at once (no streaming benefit); C uses wrong WritableStream type.

4. Final Answer:

   Use ReadableStream with async start(controller), loop over items, enqueue JSON strings, and close after all. -> Option D

5. Quick Check:

   Stream chunks in loop with ReadableStream = D [OK]

Hint: Stream each item chunk inside async start, then close stream [OK]

Common Mistakes:

• Sending all data at once, losing streaming benefit
• Using WritableStream instead of ReadableStream
• Making multiple fetch calls instead of streaming