Processing a 2GB CSV in Node Without Running Out of Memory
The article discusses how to efficiently process a large 2GB CSV file in Node.js without running out of memory. It highlights the pitfalls of loading the entire file into memory and suggests using generator functions to handle data sequentially. By processing one row at a time, developers can avoid excessive memory usage and improve performance.
- ▪Loading a 2GB CSV file into memory can lead to JavaScript heap out of memory errors.
- ▪Using generator functions allows for processing data sequentially without holding the entire file in memory.
- ▪The article emphasizes that only one row needs to be in memory at a time to sum a column.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 480406) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Coded Parts Posted on May 30 Processing a 2GB CSV in Node Without Running Out of Memory #node #javascript #generators #performance Why the obvious approach crashes, and how a few generator functions keep memory flat no matter how big the file gets. A while back I had to do something that looked trivial on paper. Read a CSV export, filter the rows we cared about, sum one column, write a small report. The kind of thing you bang out in ten minutes. The file was around 2GB.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
