Flexible Magnolia Hosting       in the Cloud     Mathias Seiler
About us        ☁    VMware vCloud™ Powered Service Provider        ☁    Hosting hundreds of Magnolia CMS instances       ...
Cloud starts today. With us.http://www.mirocloud.com/
A few words on Java        ☁    Fast and scalable        ☁    Stable        ☁    But ... Eats memory for breakfastwww.miro...
A few words on Java        ☁    Start with 256M RAM at least (!)        ☁    For STK: 512M or more        ☁    (btw: not t...
How to scale?        ☁    Throw hardware at the problem?        ☁    Try to optimize memory allocations?        ☁    Magic...
Do something crazy!www.mirocloud.com
But before that ...
About Memory        ☁    How is JVM memory “seen”             by the OS (kernel) ?www.mirocloud.com
About Memory        ☁    Like a big chunk of memory assigned to a             process.        ☁    Kernel won’t manage it ...
Quick poll        ☁    Who’s using VMware (vSphere) ?        ☁    Hyper-V ?        ☁    Xen ?        ☁    KVM?        ☁   ...
EM4J        ☁    Part of VMware vFabric        ☁    Elastic Memory for Java        ☁    Java Heap Memory Poolingwww.mirocl...
Pooling memory?                    Memory Poolwww.mirocloud.com
How does it work?        ☁    Ballooning        ☁    Coordination with the Hypervisorwww.mirocloud.com
How does it work?                     OS                    Balloonwww.mirocloud.com
How does it work?                     OS                     JVM                    Balloonwww.mirocloud.com
How does it work?                     OS                     JVM                    Balloonwww.mirocloud.com
How does it work?        ☁    Balance memory between VMs and hosts*             (*taking VMware’s Distributed Resource    ...
How does it work?                    OS      OS        OS                    JVM    JVM       JVM                Balloon  ...
How does it work?                    Magnolia ...                    Balloon.jar                    vFabric tc            ...
Why?        ☁    Less memory = less cost/power/licenses ...        ☁    (but the most interesting ...)        ☁    It’s el...
What does this mean?        ☁    You can run applications ...        ☁    ... more dynamically        ☁    ... with less o...
What does this mean?        ☁    In fact:        ☁    We even allocate more memory             than before!        ☁    Be...
Numbers        ☁    You can save up to 40% of system memory             (at least that’s what we measured)        ☁    Eve...
“Elastic”        ☁    real dynamic workload distribution             (“cloud”)        ☁    traffic / workload “spikes” fla...
Interesting notes        ☁    It’s adaptive by design        ☁    = very little performance impact        ☁    more “busy”...
Questions?www.mirocloud.com
Upcoming SlideShare
Loading in …5
×

Flexible Magnolia Hosting in the Cloud

808 views

Published on

By pooling JVM memory across virtual machines it's possible to operate flexible Magnolia CMS instances and overcome typical Java issues like out-of-memory events or resource over-provisioning.

Being experienced in providing IaaS, we can show you real-world examples of how we do it and what benefits can be achieved by hosting Magnolia CMS in a VMware vCloud™ Powered environment.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
808
On SlideShare
0
From Embeds
0
Number of Embeds
247
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Flexible Magnolia Hosting in the Cloud

  1. 1. Flexible Magnolia Hosting in the Cloud Mathias Seiler
  2. 2. About us ☁ VMware vCloud™ Powered Service Provider ☁ Hosting hundreds of Magnolia CMS instances ☁ (Hosting Magnolia’s server infrastructure too)www.mirocloud.com
  3. 3. Cloud starts today. With us.http://www.mirocloud.com/
  4. 4. A few words on Java ☁ Fast and scalable ☁ Stable ☁ But ... Eats memory for breakfastwww.mirocloud.com
  5. 5. A few words on Java ☁ Start with 256M RAM at least (!) ☁ For STK: 512M or more ☁ (btw: not taking Derby into account)www.mirocloud.com
  6. 6. How to scale? ☁ Throw hardware at the problem? ☁ Try to optimize memory allocations? ☁ Magic?www.mirocloud.com
  7. 7. Do something crazy!www.mirocloud.com
  8. 8. But before that ...
  9. 9. About Memory ☁ How is JVM memory “seen” by the OS (kernel) ?www.mirocloud.com
  10. 10. About Memory ☁ Like a big chunk of memory assigned to a process. ☁ Kernel won’t manage it (except if swapping!) ☁ No visibility ☁ Extremely painful if it’s virtual memory (on a hypervisor, set full reservations)www.mirocloud.com
  11. 11. Quick poll ☁ Who’s using VMware (vSphere) ? ☁ Hyper-V ? ☁ Xen ? ☁ KVM? ☁ Any other virtualization technology?www.mirocloud.com
  12. 12. EM4J ☁ Part of VMware vFabric ☁ Elastic Memory for Java ☁ Java Heap Memory Poolingwww.mirocloud.com
  13. 13. Pooling memory? Memory Poolwww.mirocloud.com
  14. 14. How does it work? ☁ Ballooning ☁ Coordination with the Hypervisorwww.mirocloud.com
  15. 15. How does it work? OS Balloonwww.mirocloud.com
  16. 16. How does it work? OS JVM Balloonwww.mirocloud.com
  17. 17. How does it work? OS JVM Balloonwww.mirocloud.com
  18. 18. How does it work? ☁ Balance memory between VMs and hosts* (*taking VMware’s Distributed Resource Scheduler into account)www.mirocloud.com
  19. 19. How does it work? OS OS OS JVM JVM JVM Balloon Balloon Balloonwww.mirocloud.com
  20. 20. How does it work? Magnolia ... Balloon.jar vFabric tc OS ESXiwww.mirocloud.com
  21. 21. Why? ☁ Less memory = less cost/power/licenses ... ☁ (but the most interesting ...) ☁ It’s elastic!www.mirocloud.com
  22. 22. What does this mean? ☁ You can run applications ... ☁ ... more dynamically ☁ ... with less or no OOM events at all ☁ ... without over-allocating memorywww.mirocloud.com
  23. 23. What does this mean? ☁ In fact: ☁ We even allocate more memory than before! ☁ Because that allocation is the maximum memory the JVM is going to consume.www.mirocloud.com
  24. 24. Numbers ☁ You can save up to 40% of system memory (at least that’s what we measured) ☁ Even if you allocate more than you did beforewww.mirocloud.com
  25. 25. “Elastic” ☁ real dynamic workload distribution (“cloud”) ☁ traffic / workload “spikes” flattened out ☁ easy configurationwww.mirocloud.com
  26. 26. Interesting notes ☁ It’s adaptive by design ☁ = very little performance impact ☁ more “busy” JVMs get more memory over timewww.mirocloud.com
  27. 27. Questions?www.mirocloud.com

×