4 ms·
Not Docker, webpack. Your run-of-the-mill webpack dev server will happily gulp gigabytes of RAM, and pray that your frontend dev stack only runs one of them. Yo
by axlee 4y ago
Not Docker, webpack. Your run-of-the-mill webpack dev server will happily gulp gigabytes of RAM, and pray that your frontend dev stack only runs one of them. Your IDE will probably use a few more gigabytes on top of that for static analysis and autocompletion, and that's how you need at least 8-10GB to run develop your average mid-size web app without swapping.
- nicoburns 4y agoMy webpack config for a fairly large app run under a single GB, and performance on my m1 pro machine is so good that I have it permanently running the background. Maybe you need to optimise your config?
- postalrat 4y agoHow about the rest of the app? Database servers, other servers, more servers, other services, etc all running in docker.
- axlee 4y agoWhether they run in docker or not has very little impact on the memory usage, especially on Linux where the overhead is tiny. In VMs, YMMV.