We recently migrated one of our high-traffic content sites from Next.js Page Router (SSR) to Next.js 15 App Router using Server Components (RSC). After 3 weeks of running in production, I gathered some interesting insights regarding core web vitals, server-side memory leaks, and compilation sizes. Here is a breakdown of what improved and what got slightly worse.
Fascinating analysis, Jane! What were the memory leak findings? Did you discover if it was caused by the routing cache or custom fetch cache headers? Next.js routing cache is notoriously hard to configure correctly.
Use ``` code ``` for syntax highlighting