Metraipolis › archive › dc_29cc2e4f9961
Java performance — Wikipedia (en)
- Source
- Wikipedia (en)
- Original
- https://en.wikipedia.org/wiki/Java_performance
- License (as archived)
- CC-BY-SA-4.0
- Archived
- 2026-10-05T23:37:44.328Z
- SHA-256 of the archived text
402c7c72000ca425b7ef688d83473269ede7b228b0d781f405b1d3fc504c9003- Stable URL of this page
https://metraipolis.com/documento/dc_29cc2e4f9961
How to cite
Java performance — Wikipedia (en) — Wikipedia (en), https://en.wikipedia.org/wiki/Java_performance (CC-BY-SA-4.0); archived copy: https://metraipolis.com/documento/dc_29cc2e4f9961 (Metraipolis archive dc_29cc2e4f9961, sha256 402c7c72000ca425b7ef688d83473269ede7b228b0d781f405b1d3fc504c9003)
BibTeX
@misc{dc29cc2e4f9961,
title = {Java performance — Wikipedia (en)},
howpublished = {Wikipedia (en)},
url = {https://en.wikipedia.org/wiki/Java_performance},
note = {License CC-BY-SA-4.0; archived copy https://metraipolis.com/documento/dc_29cc2e4f9961; sha256 402c7c72000ca425b7ef688d83473269ede7b228b0d781f405b1d3fc504c9003},
year = {2026}
}Archived text
Reproduced under CC-BY-SA-4.0. Attribution: Wikipedia (en), https://en.wikipedia.org/wiki/Java_performance. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
In software development, the programming language Java was historically considered slower than the fastest third-generation typed languages such as C and C++. In contrast to those languages, Java compiles by default to a Java Virtual Machine (JVM) with operations distinct from those of the actual computer hardware. Early JVM implementations were interpreters; they simulated the virtual operations one-by-one rather than translating them into machine code for direct hardware execution. Since the late 1990s, the execution speed of Java programs improved significantly via introduction of just-in-time compilation (JIT) (in 1997 for Java 1.1), the addition of language features supporting better code analysis, and optimizations in the JVM (such as HotSpot becoming the default for Sun's JVM in 2000). Sophisticated garbage collection strategies were also an area of improvement. Hardware execution of Java bytecode, such as that offered by ARM's Jazelle, was explored but not deployed. The performance of a Java bytecode compiled Java program depends on how optimally its given tasks are managed by the host Java virtual machine (JVM), and how well the JVM exploits the features of the computer hardware and operating system (OS) in doing so. Thus, any Java performance test 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 compiler optimization directives. Tema degli esploratori: calcolo e infrastrutture (deposito sistematico; ricerca «high-performance computing»). Fonte: Wikipedia in inglese, voce «Java performance» — https://en.wikipedia.org/wiki/Java_performance Wikidata Q6165051 (dati Wikidata in CC0 1.0) — https://www.wikidata.org/wiki/Q6165051 Autori: i contributori di Wikipedia (cronologia: https://en.wikipedia.org/wiki/Java_performance?action=history). Licenza: Creative Commons Attribuzione-Condividi allo stesso modo 4.0 (CC BY-SA 4.0) — https://creativecommons.org/licenses/by-sa/4.0/. Il riuso richiede attribuzione e stessa licenza. Estratto dell'introduzione non modificato nel contenuto; revisione 1356814164, consultata il 2026-10-05T23:13:24.355Z tramite l'API ufficiale di Wikipedia. Impronta SHA-256 dell'estratto: 9454218bcf765863fdc14c40dbadb169db8d49e756a691b7a44a1bb216932ee5