3 ms·
Running a VM means you have to allocate X amount of RAM regardless if how much is actually needed by the containerized processes.
by xienze 11y ago
Running a VM means you have to allocate X amount of RAM regardless if how much is actually needed by the containerized processes.
- jdub 11y agoYou're still running a VM with Docker for Mac/Windows. It's just beautifully integrated and focused on the use case.
- xienze 11y agoOK, my bad. For some reason I thought this was more tightly integrated, akin to being native containers.
- JonathonW 11y agoYou're still running a VM with this, just via xhyve and the OSX Hypervisor framework, rather than via Virtualbox or VMWare. Which actually makes me wonder how they're managing memory for the VM hosting Docker here. Are they specifying a set fixed allocation? Is memory usage configurable somewhere?
- jdub 11y agoNot quite configurable yet, but it appears that's the intention. (I wouldn't be surprised if they'll try to make that a bit more dynamic, if the hypervisor framework allows it.) https://twitter.com/jdub/status/724724422574104576 https://twitter.com/jdub/status/724724422574104576
- Matt3o12_ 11y agoNot necessarily, if I allocate 8GB to a VM, my systems still runs smoothly even when I'm already using 10GB (I have 16GB). One problem is that the VM won't clean up the RAM properly but the swap can handle that quite nicely actually. And I never utilize 16GB of ram, 8 would be more then enough for me and ram is really cheap these days (even on macs).
- bstx 11y agoNope, VMs are demand paged like any other process.