# Next.js 8 Webpack Memory Improvements

DevFeed: [Next.js 8 Webpack Memory Improvements](<https://devfeed.tech/articles/next-js-8-webpack-memory-improvements-3290.md>)

Original publisher: [Read original article](<https://nextjs.org/blog/webpack-memory>)

Author: Tim Neutkens

Published: 2019-02-19T14:00:00Z

Content type: article

Language: en

Sources: [Next.js Blog](<https://devfeed.tech/sources/next-js-blog.md>)

Topics: [Next.js](<https://devfeed.tech/topics/next-js.md>), [Webpack](<https://devfeed.tech/topics/webpack.md>), [build performance](<https://devfeed.tech/topics/build-performance.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [Chrome](<https://devfeed.tech/topics/chrome.md>)

Tags: [blog-post](<https://devfeed.tech/tags/blog-post.md>), [build](<https://devfeed.tech/tags/build.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [framework](<https://devfeed.tech/tags/framework.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [profiling](<https://devfeed.tech/tags/profiling.md>), [web-applications](<https://devfeed.tech/tags/web-applications.md>), [webpack](<https://devfeed.tech/tags/webpack.md>)

## AI overview

This article explains how Next.js 8 reduced build-time memory usage by optimizing webpack. Profiling revealed that concurrent generation and writing of many page assets caused large memory spikes. Limiting concurrent writes to 15 split the allocation into smaller pieces and improved build memory behavior.

## Source excerpt

Recently Next.js 8 was introduced. The release included a massive build-time memory usage reduction. This blog post will explore how we have helped optimize webpack for the community.