Quote from
pjhunter on February 16, 2020, 8:00 pm
Folks,
I have an Antsle D+ with 64GB of memory. I have 4 antlets defined (see attachment). Two are running at present. The allocated ram should be only 40GB (24+16). However, the antsle dashboard is reporting 98% of the ram being used. When I try to start one of the other antlets the Antman reports that my RAM is oversubscribed and I have to stop one or more antlets to free up resources! Why specify RAM limits if Antman ignores them and allocates unused memory to the running antlets? Coratina in particular (24GB allocated) is a production server and it is highly inconvenient to stop it to launch others.
I've also noticed that when ONLY Coratina is running, it too will consume 98% of available ram. It doesn't happen immediately, but over the course of a couple of hours the % allocated grows from 40% (expected) to 98%. Coratina is a 2016 WinServer instance. Leccino is a 2010 Windows 10 Pro instance.
What gives?
Folks,
I have an Antsle D+ with 64GB of memory. I have 4 antlets defined (see attachment). Two are running at present. The allocated ram should be only 40GB (24+16). However, the antsle dashboard is reporting 98% of the ram being used. When I try to start one of the other antlets the Antman reports that my RAM is oversubscribed and I have to stop one or more antlets to free up resources! Why specify RAM limits if Antman ignores them and allocates unused memory to the running antlets? Coratina in particular (24GB allocated) is a production server and it is highly inconvenient to stop it to launch others.
I've also noticed that when ONLY Coratina is running, it too will consume 98% of available ram. It doesn't happen immediately, but over the course of a couple of hours the % allocated grows from 40% (expected) to 98%. Coratina is a 2016 WinServer instance. Leccino is a 2010 Windows 10 Pro instance.
What gives?
Uploaded files: