yceffort
05 POSTS

Memory 1

  • ◆ Page Preservation in Next.js Part 2
    #nextjs#memory#web-performance

    Why Did Next.js's Last Three Leave Nine Posts Behind?

    Next.js is said to preserve the last three pages, yet nine posts remained on this blog. A sequential navigation experiment measures how far preservation reaches, then looks at managing memory by separating work to stop when hidden from state worth keeping.

    16 min read
  • ◆ Kubernetes for Frontend Developers Part 6
    #memory#nodejs#kubernetes

    Why Is Your Node.js Pod That Size? Sizing Measured Firsthand, from NODE_OPTIONS to Pod Count

    I added one GC tuning flag to the same workload and peak RSS rose from 201MB to 593MB while the live data stayed the same. This post measures V8 New Space directly to trace why, and proposes three criteria frontend developers can use to size a Node.js pod.

    Updated 45 min read
  • #memory#web-performance#design-patterns

    Preventing Memory Leaks with IntersectionObserver Singleton Pattern and WeakMap

    How to efficiently observe hundreds of elements while preventing memory leaks

    13 min read
  • #web-performance#memory#async

    How to Efficiently Process Massive JSON Responses

    How to survive when JSON.parse() becomes overwhelming

    18 min read
  • #memory#nodejs#v8

    A Guide to Node.js Memory Limits and Leak Tracking

    A look at V8's generational garbage collection, adjusting heap memory limits, and practical ways to diagnose memory leaks.

    7 min read