VPS Burst versus Swap Memory Management
Date Added : Nov 16, 2010 | Author : Admin |
 |
Burst versus swap discussions are normally - comparisons of OpenVZ versus Xen memory management. There are advantages and disadvantages to each, with burst associated with VZ and swap to Xen. Assuming everything else is equal, which would you consider is the better option - 1024MB guaranteed (SLM) or 768MB guaranteed (burstable to 2048MB)
I just read of an experiment - pairing the two technologies under load conditions. The test involved an OpenVZ container (512MB dedicated RAM with 512MB burst) versus a XEN based VPS (768MB with swap). A basic Debian 5 64 bit OS was installed on each with LAMP, email and Jabber/XMPP. The total OpenVZ memory usage equaled 445MB versus XEN's 296MB.
So what can we take away from this test? If you're running Java or other applications that tend to allocate large amounts of virtual memory, OpenVZ containers (without burst) will have less guaranteed memory available. Enter burst .. OpenVZ needs an appropriate amount of burst (usually 1.5 to 2 times the guaranteed).
Beyond guaranteed to burst and swap - access latency on RAM (burst) is measured in nanoseconds whereas swap (HDD) is measured in milliseconds (much much slower). Swap is slow, so you want ample guaranteed (SLM) to handle your applications. Plus, your system cannot execute stuff out of swap. It has to be in active RAM to execute. With both burst and swap, you want just enough allocation to handle inactive data, keeping as much active data in guaranteed RAM as possible.
Overselling can be - an issue with OpenVZ, e.g., killing your application if it bursts beyond the guaranteed resource allocation, instead of simply slowing down as with a true dedicated server. The kernel of Virtuozzo cannot be modified as it's based on an OS template. By contrast, Xen doesn't allow overselling, so a physical server with 16GB of RAM would be limited to 64 x 256MB virtual machines. Plus, XEN allows you to fully modify the kernel, so advanced users can compile and load their own modules, resulting in properly virtualized memory, IO and scheduler - that's stable and predictable.
About the Author:
Steve Bloemer is the Editor for WDTalk which is a web development blog. He's published hundreds of articles covering business tips, web design, SEO and web hosting.
http://wdtalk.com |
|
