IBM, Java and POWER Linux IBM Corporation

Transcription

1 IBM, Java and POWER Linux IBM Corporation

2 IBM and Java Java tm is critically important to IBM Provides fundamental infrastructure to hundreds of products within IBM software portfolio Delivers standard development environment The Virtual Machines enable cost effective multi platform support Delivered to Independent Software Vendors supporting IBM server platforms IBM is investing strategically in Java technology and virtual machines Available on more platforms than any other vendor Seamless exploitation of emerging hardware World class service and support Continuous investment in performance, reliability and serviceability IBM supports accelerated and open innovation in runtime technologies Broad participation of relevant standards bodies such as JCP, OSGi, Eclipse IBM Corporation

3 Java Technologies World Wide Organisation Toronto IBM JIT compilation IBM XML parsing Rochester IBM iseries tm development Ottawa IBM J9 Java tm Virtual Machine IBM Java tm ME libraries Poughkeepsie z/os system test IBM zseries tm system Test Hursley Consumability tooling VM Servicability Portoflio Management Customer service Shanghai IBM Java tm SE Libraries Globalization Specialized testing Phoenix IBM Javat tm ME development Austin IBM Java tm and XML security IBM pseries tm system and performance test Bangalore IBM Java tm SE Libraries Integration testing Customer service Field release development IBM Corporation

4 IBM s Approach to Java Technology Quality Engineering Performance Security Reliability Serviceability Listen to and act upon market requirements World class service and support Available on more platforms than any other vendor Optimised for customers key platforms Write Once Run Anywhere Embedded in IBM s broad middleware Reference Java Technology (Sun, OSS, Others) IBM Java Technology Centre IBM Java portfolio Production Requirements IBM Software Group IBM Server Technology Group ISVs IBM Clients IBM Corporation

5 Relationship between IBM and Oracle/OpenJDK User Code Application Code Java Runtime JV M TI Java Class Libraries Class Library Natives S E C O R B X M L User Natives Core VM Testarossa JIT J9 Virtual Machine Operating System AIX IBM i (PASE) Linux Windows z/os = User Code = OpenJDK Technology PPC32 PPC64 x86-32 x86-64 PPC-32 PPC x86-32 x = IBM Standards Compliant Technology = Operating System 2012 IBM Corporation

6 Java delivery roadmap SUN/ Oracle SDKs Sun Supported Platforms at Java 5.0 Solaris x64 Solaris SPARC Solaris x86 Windows IA32 Windows AMD64 Windows EAMT64 Linux IA32 Linux AMD64 Linux EAMT64 Java 5.0 delivers New Language features Autoboxing Enumerated types Generics Meta Data Java 6.0 delivers Performance improvements Improved UI Client WebServices Support Java 7.0 delivers Ease of development: Project Coin Improved scalability Non-Java language support on 12 platforms on 15 platforms 5.0 on 18 platforms 6.0 on 20 platforms 7.0 on 20 platforms 8.0 on 20 platforms? IBM SDKs IBM Java 5.0 features Improved performance Generational Garbage Collector Shared classes support New JIT technology First Failure Data Capture Configurable Trace Full Speed Debug Hot Code Replace Common runtime technology ME, SE, EE IBM Supported Platforms from Java 6.0 AIX PPC 32 AIX PPC 64 POWER Linux 32 POWER Linux 64 zlinux 31 zlinux 64 HP-UX PA-RISC 32 HP-UX PA-RISC 64 HP-UX IA64 zos 31 Solaris x64 Solaris SPARC Solaris x86 Windows IA32 Windows AMD64 Windows EAMT64 Linux IA32 Linux AMD64 Linux EAMT64 zos 64 IBM Java 6.0 features Improvements in Platform coverage Performance Serviceability tooling New Functionality IBM WebSphere Real- Time V1.0 IBM Java 7.0 features New balanced GC Improved data sharing Significant diagnostic improvement WebSphere RealTime v3 evaluation technology IBM Corporation

7 IBM Java Innovations IBM Corporation

8 Memory Sharing and Multi-Tenancy J9 JVMs using sharing to reduce costs Shared classes cache for read-only shared artifacts (bytecodes) Dynamic AOT - reuse JIT code from multiple JVMs Reduce memory use by 20%, improve startup time % Cloud? JVMs starting up at the same time Compile code once, run faster! JVM JVM JVM JVM JVM JVM JVM JVM JVM JVM JVM JVM JVM JVM JVM JVM shared index Verified bytecodes Shared Classes Cache AOT Ahead Of Time (JIT code saved for next JVM) IBM Corporation

9 Memory Sharing and Multi-Tenancy Multi-Tenant JDK: JVM-level virtualization vs. middleware virtulization JVM allows for multiple isolated middleware/application instances Solved isolation problems: Middleware stack appears dedicated JVM, Class and Compiled Code sharing Resource control provided by JVM CPU, Memory, Network, I/O App App Middleware (e.g. WAS) OS Image Hardware Shared Middleware App vjvm OS Image Hardware App Middleware Middleware vjvm Multitenant JVM Multi Tenant JVM Operating System Mechanism File System Isolation Disk Quotas I/O Rate Limiting Memory Limits CPU Quotas Network Isolation Live Migration AIX LPAR Y Y Y Y Y Y Y WPAR Y Y Y Y Y Y Y MT-JDK NY NY Y Y Y NY N Linux VMware ESX Y Y Y Y Y Y Y Open VZ Y Y Y Y Y Y Y MT-JDK NY NY Y Y Y NY N IBM Corporation

10 Memory Sharing and Multi-Tenancy Multi-Tenant JDK for High Density Java: Multiple applications run in one daemon JVM Applications appear as if they are running in a dedicated JVM Provides Isolation and Resource Controls: CPU, Heap Memory, Threads, Files, Network Running the Multi-Tenant JDK: Opt-in by adding Xmt JVM will locate/start daemon Tenant created inside javad daemon Adding a second tenant: Opt-in by adding Xmt JVM will locate/start daemon Tenant created inside javad daemon One copy of common code Most runtime structures shared Tenant 1 Tenant 2 javad One copy of common code lives in the javad process IBM Corporation

11 Interoperability: PackedObjects Proposed Language extension to support Compact data structures with controlled memory layout to reduce memory overhead High performance standardized direct access to native memory (off-heap) High performance serialization and I/O of Java objects with in-place use avoids marshalling apoint aline int x apackedline int y Point s Point e apoint int x int y int x int x int y int final class PackedPoint extends PackedObject { int x; int final class PackedLine extends PackedObject { PackedPoint s; PackedPoint e; } apackedline int x int y int x int y Object header Object data PackedPoint s PackedPoint e IBM Corporation

12 Interoperability: PackedObjects Performance Relative Improvement (normalized to traditional Java) Trade Data PackedObjects vs Traditional Java Footprint Elapsed time Traditional Java PackedObjects Online Trade Record Parsing * 50Mbytes of trade objects Packed prototype vs standard Footprint is 20% better Elapsed time is 95% better Improvement * see (Note this kind of result require you to be a member of the J9 VM team until we standardize this feature) IBM Corporation

13 Monitoring and Diagnostics: Health Center Live monitoring tool with very low overhead Pre-installed in IBM JDKs since Java 5 Enable at startup: -Xhealthcenter Enable at runtime: java -jar healthcenter.jar ID=<pid> All data available via a public API to build your own monitoring solutions Environment reporting Detects invalid Java options Detects options which may hurt performance or serviceability Useful for remote diagnosis of configuration-related problems Class loading visualization Shows all loaded classes Shows load time Identifies shared classes File I/O Monitor application file open/close events as they occur Lists currently open files IBM Corporation

14 Monitoring and Diagnostics: Health Center Garbage Collection visualization Visualizes heap usage and gc pause times over time Identifies memory leaks Suggests command-line and tuning parameters Java Object allocation profiling by allocating code or type Native Memory Detect native memory leaks in application Determine if external forces are using more memory Memory counters showing which parts of the JVM are using the most native memory Threads view List of current threads and states Number of threads over time See contended monitors IBM Corporation

15 Monitoring and Diagnostics: Health Center Method Profiling Always-on profiling shows application activity Identifies the hottest methods in an application Full call stacks to identify where methods are being called from and what methods they call No byte code instrumentation, no recompiling Java Lock Profiling Always-on lock monitoring Quickly allows the usage of all locks to be profiled Helps to identify points of contention in the application that are preventing scaling Live control of application Trigger dumps Enable verbosegc collection IBM Corporation

16 Monitoring and Diagnostics: Health Center Application Throughput (percentage of baseline) Baseline Dormant (level=off) Network Client Headless client (level=headless) Headless client with ZIP (level=headless) Measured using WebSphere App Server and the DayTrader benchmark with 50 clients Running WAS 8.5.5, IBM Java 7 SR5, AIX 7.1, POWER7 Throughput determined by number of completed transactions on 4 saturated CPUs IBM Corporation

17 Performance SPECjEnterprise 2010 SPECpower_ssj2008 EjOPS/processorcore Fastest Competitor 823 J9 IBM 59% faster than fastest competitor overall ssj_ops/watt Best Competitor 5689 J9 10% better than best competitor J9 Results from as of 09/11/2013. J9 SPECjEnterprise 2010 based on IBM PowerLinux 7R EjOPS/core. Competitor based on Sun Server X EjOPS/core. Results from as of 9/11/2013, based on Fujitsu s PRIMERGY TX200 S7 SPEC, SPECjEnterprise 2010 and SPECpower_ssj are registered trademarks of the Standard Performance Evaluation Corporation. For more information. see IBM Corporation

18 Java on POWER IBM Corporation

19 Performance: Automatic from the JIT compiler interpreter Methods start out being interpreted cold warm hot After N invocations methods get compiled at cold or warm level Sampling thread used to identify hot methods profiling Methods may get recompiled at hot or scorching levels scorching Transition to scorching goes through a temporary profiling step 2010 IBM Corporation

20 J9 JVM Compile Time Connector cold warm hot scorching small AOT wcode FSD Optimizer Block Hoisting Java Bytecode IR Generator Optimizations Testarossa Dynamic Compilation Java JIT on POWER Profiler Interpreter Profile Info Sampling Thread Connector Options Object Model Profile Manager Hardware counters Language Specific Code Generators C library functions Threading POWER Code Generator JIT Profile Info Tracing RT Connectors RT Helpers Runtime Metadata code 2010 IBM Corporation

21 JIT Compiler exploitation of Power 7 New prefetching capabilities Transient prefetch: data which has no temporal locality Stride-N prefetch: data accessed in non-contiguous pattern Partial cacheline prefetch: data which has poor spatial locality Extended divide instructions For multiple precision library 3X better performance for 64bit divide in 32bit mode Conversion between integer and float Complete set of operations Out-of-line code will be gradually phased out Bit permutation and popcount instructions Complementary to crypto accelerators Accelerators through PKCS#11 standard providers Instructions through inlining java code Vector-scalar extension (VSX) to PowerPC architecture 64 registers Complete set of operations on double/single precision float BCD assist Better DFP code Exploited through Java BigDecimal 2010 IBM Corporation

22 Performance: Some buttons you can press Large Pages: Larger pages allocated by the OS means more efficient cache locality Default is currently 64k pages, but you can move to 16MB or 16GB Possible improvement: ~10% GC Policy and Tuning Settings: 4 different policies based loosely on scenario: optthruput, optavgpause, gencon and balanced Default is gencon and is appropriate for (almost) all scenarios Performance can be improved with larger nursery heaps Possible improvement: ~5% GC helper threads GC is parallel, and will default to one thread per processor For deployments with multiple JVMs on one partition, this should be reduced Possible improvement: ~small Java performance is largely provided out of the box Biggest gains are usually in tuning/modifying your application Health Center provides insight into where optimizations can be made 2010 IBM Corporation

23 Questions? IBM Corporation