Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Method to optimze VM system perfomance by RAM Memory Swaping Out

IP.com Disclosure Number: IPCOM000242952D
Publication Date: 2015-Sep-02
Document File: 3 page(s) / 50K

Publishing Venue

The IP.com Prior Art Database

Abstract

If a machine won't be utilized (but not 100% down) for a longer period it is proposed to swap out whole machine's memory for this time and save Host Physical RAM Memory resources. Despite the fact that remote access and effective utilization of this machine (when VM is swapped out) will be more difficult, this VM will be still able to keep most of the basic life functions like system date and time.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 3

Method to optimze VM system perfomance by RAM Memory Swaping Out

In nowadays Data Center's technologies Virtual Environment build on Cloud or directly on single Hypervisor are the most desired solutions by companies across the globe. This approach helps to utilize resources more efficient then any time before. However this approach still has one biggest bottleneck: memory utilization.

Machines with Idle processes or currently unutilized by any user can release almost all the resources (like CPU, disk read/write) except consumed physical memory needed for virtual machine to preserve continuity. This consumption can be wide across many OS types. From hundreds of megabytes on Linux to many gigabytes on newest Windows machines.

This consumed memory often remains in unchanged state for hours. Across all available advanced memory management techniques, migrating VM's RAM to Host SWAP is the last resort used only when all resources are empty and all other advanced techniques has been used (other techniques: transparent memory page sharing, ballooning, etc). Reason for that is that memory swapping process is done page by page (MB by MB) and usability of that approach is limited.

The problem comes with speed fact - usual Server RAM is about 100.000 faster than usual disk. And moving memory page by page is something that can bring machine down for days.

What if we could swap out whole machine memory at once? But if we know that this machine won't be utilized (but not 100% down) for next 16 hours or next 2 weeks we could swap out whole machine's memory for this time and save Host Physical RAM Memory resources.

Biggest advantage of this method is that despite the fact that remote access and effective utilization of this machine (when VM is swap out) will be very difficult this VM will be still able to keep most of the basic life functions like: system date and time (for example very important to keep Database in the consistent state).

1


Page 02 of 3

Flow Chart

Scenario (based on Flow Char...