Chewing RAM

[brorbw]

I've had a simple webserver running for a couple of days or so. Nothing major, just serving pages from my mac. Hyperkit is eating more that 2gb of ram?
The setup is (nodejs + a mongo db offsite) what gives?
https://imgur.com/a/kxeZR
Im dont know what information about the process would be helpfull, if you have any suggestions, i would try to recreate the scenario.

[ijc]

The RAM used by hyperkit should be fully swappable, please see #67 (comment) and and docker/for-mac#178 (comment) for details of what that means and why we don't consider an apparently large process size as an issue in the first instance.

I'm going to preemptively close but please do reopen if you find that the memory is locked down somehow.

Note: If you are consuming Hyperkit via Docker for Mac (as opposed to directly for running your own VM) then please open an issue at https://github.com/docker/for-mac instead of reopening here.

[rsn8887]

I don't understand how can swapping all this leaked memory to disk be a solution? Disk space is also limited after all...

[brorbw]

He is saying that it should be swapped to disc and that this would have no impact on the memory available to the system. But in my case the memory was indeed locked by hyperkit, and not swapped to the disk.
I used hyperkit through docker and that might have made an impact on the memory usage somehow. Never the less, I learned to live with it. You gotta love scalable virtual servers ✌️