The memory footprint of node modules
summary
Scripts that require heavy modules load tens of megabytes each so measuring initial process RSS matters: use the uploader description methods and tools like npm ls, dependency-check, npm dedupe and size analyzers (analyze-module-size, cost-of-module) or the module-footprints CLI that compares memory before/after require. Replace bulky libraries with submodule requires (lodash/chunk) or native APIs (Array.find, core http/https) or rewrite small helpers. Result is concrete: per-script memory drops from ~25–26MB to under 10MB, allowing ~6,400 concurrent scripts in the author’s test.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:07Load Testing
- 3:38Goals
- 4:42Scale Horizontally
- 7:33Dependency Check Cli
- 9:06Duplicate Baggage
- 11:31Baggage Size
- 13:19Module Footprints
- 16:34Baseline Memory Footprint of Express
- 18:44Recap
related talks
42mHoney, I shrunk the node_modules!
02h 24mHow to Node.js - Part 2
30mWhat's Really Going on Inside Your Node_Modules Folder
18mNode.js Module: I Choose You!
32mLet's Tree-shake it...
01h 02mThe Wrong Kind of Fast: Embracing Evidence-Based Architecture
48mThe Node Module Diaries: Large App Architecture from the Trenches
21mHealthy and Fit Wombats for the Greater Good!