Java performance

In <a href="/facts/Software_development/UUfsAaYY">software development</a>, the programming language <a href="/facts/Java_/9ScgFyAL">Java</a> was historically considered slower than the fastest <a href="/facts/Third-generation_programming_language/v6N8rpno">third-generation</a> <a href="/facts/Type_system/Tz0bAMS9">typed</a> languages such as <a href="/facts/C_/Ky2No763">C</a> and <a href="/facts/C%2B%2B/Et0F2qn9">C++</a>. In contrast to those languages, Java compiles by default to a <a href="/facts/Java_Virtual_Machine/l9Nzrsun">Java Virtual Machine</a> (JVM) with operations distinct from those of the actual computer hardware. Early JVM implementations were <a href="/facts/Interpreter_(computing)/JB85fbyb">interpreters</a>; they simulated the virtual operations one-by-one rather than translating them into <a href="/facts/Machine_code/bgdQ1Fxf">machine code</a> for direct hardware execution.
Since the late 1990s, the execution speed of Java programs improved significantly via introduction of <a href="/facts/Just-in-time_compilation/rEYDsd8l">just-in-time compilation</a> (JIT) (in 1997 for <a href="/facts/Java_version_history/Br6eHSP8">Java 1.1</a>), the addition of language features supporting better code analysis, and optimizations in the JVM (such as <a href="/facts/HotSpot_(virtual_machine)/m6vjRXvm">HotSpot</a> becoming the default for <a href="/facts/Sun_Microsystems/VJ9EzEFd">Sun</a>'s JVM in 2000). Sophisticated <a href="/facts/Garbage_collection_(computer_science)/j2vlIu7g">garbage collection</a> strategies were also an area of improvement. Hardware execution of Java bytecode, such as that offered by ARM's <a href="/facts/Jazelle/CCA7g8wC">Jazelle</a>, was explored but not deployed.
The <a href="/facts/Computer_performance/td1qKox4">performance</a> of a <a href="/facts/Java_bytecode/Nh1qKH4y">Java bytecode</a> compiled Java program depends on how optimally its given tasks are managed by the host <a href="/facts/Java_virtual_machine/l9Nzrsun">Java virtual machine</a> (JVM), and how well the JVM exploits the features of the <a href="/facts/Computer_hardware/8jSjsCNv">computer hardware</a> and <a href="/facts/Operating_system/8XTuvMh2">operating system</a> (OS) in doing so. Thus, any Java <a href="/facts/Software_performance_testing/qtlCrHme">performance test</a> or comparison has to always report the version, vendor, OS and hardware architecture of the used JVM. In a similar manner, the performance of the equivalent natively compiled program will depend on the quality of its generated machine code, so the test or comparison also has to report the name, version and vendor of the used compiler, and its activated <a href="/facts/Compiler_optimization/JXnv4LUd">compiler optimization</a> directives.

Java performance open-in-new

Java performance