EVE-NG not releasing memory after all nodes are stopped

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

Post Reply
RR_Cluster
Posts: 8
Joined: Sat Sep 09, 2017 11:46 pm

EVE-NG not releasing memory after all nodes are stopped

Post by RR_Cluster » Sat Sep 09, 2017 11:57 pm

Hello,

I've been using UNL for the last year and recently started to use EVE. Something I noticed that is happening in EVE that didn't happen in UNL is EVE continues to use RAM after all nodes are stopped in a lab. For example, I'm doing a lab that is using 4GBs of RAM, after I stop all nodes EVE is still using the 4GBs of RAM instead of freeing up the memory. UNL didn't do this and I noticed it because I'm using Gadgets to monitor my system resources. Is this behavior expected? I see the same behavior from EVE using VMware player and VMware workstation.

My setup
Hardware: CPU - AMD FX-8730 (8 cores), 24GBs RAM, 512 SSD, 1 network interface
EVE-NG Running on - OS is Windows 10 and EVE is running on VMware Workstation 12 Pro, also see the same behavior in VMware player 12.5
VT-X - Enabled
EVE-NG version - 2.0.3-77. I've seen this behavior since version .71


Let me know if you need more info. This isn't a show stopper but it would be nice if EVE could release the RAM after the lab is stopped. A restart of the VM from the EVE console on the CLI doesn't resolve the issue either, only a complete power down of the VM will cause EVE to release the RAM.

mike
Posts: 135
Joined: Wed Mar 15, 2017 3:30 pm

Re: EVE-NG not releasing memory after all nodes are stopped

Post by mike » Sun Sep 10, 2017 6:15 am

Vmware does not release RAM, but reserve all you allocated to the VM.

RR_Cluster
Posts: 8
Joined: Sat Sep 09, 2017 11:46 pm

Re: EVE-NG not releasing memory after all nodes are stopped

Post by RR_Cluster » Sun Sep 10, 2017 1:18 pm

Ah that makes sense, when I didn't see this in UNL I was running Workstation 10. It looks like that changed in Workstation 12. Thanks for the response.

Post Reply