Antsle Forum

Welcome to our Antsle community! This forum is to connect all Antsle users to post experiences, make user-generated content available for the entire community and more. 

Please note: This forum is about discussing one specific issue at a time. No generalizations. No judgments. Please check the Forum Rules before posting. If you have specific questions about your Antsle and expect a response from our team directly, please continue to use the appropriate channels (email: [email protected]) so every inquiry is tracked. 

Please or Register to create posts and topics.

Memory allocation Static or Dynamic

When creating an antlet, windows or other, is it created with static or dynamic memory?

I haven't been able to determine one way of the other.

Reason I'm asking is that I have an application running on Windows 2016 server, have 12Gb allocated to the antlet, 6gb allocated to my application.  When I hook up jvisualvm to the application shows it has 6GB allocated but seems to only use 2gb.  When it finally starts using more than 2Gb...grows to 6Gb then app restarts.

I've seen similar issues when its using Dynamic memory.

If the antlet is using dynamic memory how can I make it static memory?

 

Thanks....

 

 

@Kray did you ever get an answer to this question? We would like to know so that we can manage our environments better.

Thank you in advance.

Yes, an interesting question that I would like to hear the answer to, sooner rather than later.

No, Never got an answer.

If I do, will definitely post on here to share the knowledge.

 

 

 

It sounds like the Virtio Balloon driver might be causing this "dynamic" allocation?

https://stackoverflow.com/questions/43039272/dynamic-memory-allocation-in-kvm

You can check if it is installed by going to Device Manager and looking under "Other devices".

This describes some changes you can make to your domain's XML file (using virsh edit {antlet-name}):

https://serverfault.com/questions/899760/qemu-kvm-reclamation-of-memory-from-low-use-guests

 

Before you edit your XML, I suggest doing a backup:

virsh dumpxml {antlet-name} > {antlet-name}.xml

If it's an LXC, then use:

virsh -c lxc:/// dumpxml {antlet-name} > {antlet-name}.xml

 

 

 

 

Uploaded files:
  • screencapture.png