Accelerate Your JBoss Enterprise Middleware - Red Hat Summit
Accelerate Your JBoss Enterprise Middleware - Red Hat Summit Accelerate Your JBoss Enterprise Middleware - Red Hat Summit
Accelerate Your JBoss Enterprise Middleware –Java Virtual MachineJavaJavaVirtualVirtualMachineMachine●What are Compressed Oops?● An "oop", or ordinary object pointer. An oop is normally the same sizeas the word size of the server (64-bits on X86_64, and 32-bits on X86,as an example).● So, a compressed oop is an object pointer that instead of using theword size (e.g. 64-bits), instead is compressed to 32-bits, or as a 32-bit offset from the 64-bit heap base address.● This allows a heap size of about 32 gigabytes (because they are anoffset, not a direct memory pointer).● Compressed oops is enabled by default in update 23 and above ofJDK 6. For JDK 7 its on by default as long as the maximum heap sizeis less than 32 GB's.● EAP 6.0.0.GA sets the command-line option to enable compressedoops for any Hotspot based 64-bit virtual machine.● The flag is -XX:+UseCompressedOops.● All tests in this presentation have compressed oops on, as its on bydefault now.
Accelerate Your JBoss Enterprise Middleware –Java Virtual MachineJavaJavaVirtualVirtualMachineMachine●What is large page memory?● The normal memory page size in the OS is usually 4k. When youconsider the memory footprints of modern servers, there are an awfullot of memory pages that the OS has to manage.● Large page memory, is a larger memory page than 4k.● Typically, on X86_64 systems, this is 2 MB.● Newer X86_64 systems can support 1 GB page sizes.● Another attribute of large pages (called HugeTLB in Linux), is thatthey are locked into physical memory, and cannot be swapped to disk.● This is a great attribute for the JVM.● If you have ever experienced the JVM heap being swapped to disk,you know this is a situation that often leads to the JVM crashing.● How do we take advantage of large page memory?
- Page 14 and 15: Accelerate Your JBoss Enterprise Mi
- Page 16 and 17: Accelerate Your JBoss Enterprise Mi
- Page 18 and 19: Accelerate Your JBoss Enterprise Mi
- Page 20 and 21: Accelerate Your JBoss Enterprise Mi
- Page 22 and 23: Accelerate Your JBoss Enterprise Mi
- Page 24 and 25: Accelerate Your JBoss Enterprise Mi
- Page 26 and 27: Accelerate Your JBoss Enterprise Mi
- Page 28 and 29: Accelerate Your JBoss Enterprise Mi
- Page 30 and 31: Accelerate Your JBoss Enterprise Mi
- Page 32 and 33: Accelerate Your JBoss Enterprise Mi
- Page 34 and 35: Accelerate Your JBoss Enterprise Mi
- Page 36 and 37: Accelerate Your JBoss Enterprise Mi
- Page 38 and 39: Accelerate Your JBoss Enterprise Mi
- Page 40 and 41: Accelerate Your JBoss Enterprise Mi
- Page 42 and 43: Accelerate Your JBoss Enterprise Mi
- Page 44 and 45: Accelerate Your JBoss Enterprise Mi
- Page 46 and 47: Accelerate Your JBoss Enterprise Mi
- Page 48 and 49: ManagementManagementAccelerate Your
- Page 50 and 51: Accelerate Your JBoss Enterprise Mi
- Page 52 and 53: Accelerate Your JBoss Enterprise Mi
- Page 54 and 55: Accelerate Your JBoss Enterprise Mi
- Page 56 and 57: Accelerate Your JBoss Enterprise Mi
- Page 58 and 59: Accelerate Your JBoss Enterprise Mi
- Page 60 and 61: Accelerate Your JBoss Enterprise Mi
- Page 62 and 63: Accelerate Your JBoss Enterprise Mi
- Page 66 and 67: Accelerate Your JBoss Enterprise Mi
- Page 68 and 69: Accelerate Your JBoss Enterprise Mi
- Page 70 and 71: Accelerate Your JBoss Enterprise Mi
- Page 72 and 73: Accelerate Your JBoss Enterprise Mi
- Page 74 and 75: Accelerate Your JBoss Enterprise Mi
- Page 76 and 77: Accelerate Your JBoss Enterprise Mi
- Page 78 and 79: Accelerate Your JBoss Enterprise Mi
- Page 80: References● This presentation has
<strong>Accelerate</strong> <strong>Your</strong> <strong>JBoss</strong> <strong>Enterprise</strong> <strong>Middleware</strong> –Java Virtual MachineJavaJavaVirtualVirtualMachineMachine●What is large page memory?● The normal memory page size in the OS is usually 4k. When youconsider the memory footprints of modern servers, there are an awfullot of memory pages that the OS has to manage.● Large page memory, is a larger memory page than 4k.● Typically, on X86_64 systems, this is 2 MB.● Newer X86_64 systems can support 1 GB page sizes.● Another attribute of large pages (called HugeTLB in Linux), is thatthey are locked into physical memory, and cannot be swapped to disk.● This is a great attribute for the JVM.● If you have ever experienced the JVM heap being swapped to disk,you know this is a situation that often leads to the JVM crashing.● How do we take advantage of large page memory?
Change language