如果任何人都可以简要介绍这两个 JVM 的优缺点,因为它们都依赖于标准 JVM 规范.
If anyone can give me brief information about the advantages and disadvantages of the two JVM since they all depend on the Standard JVM Specification.
JRockit 最初由 Appeal 和 BEA Systems 开发,后来被 Oracle 收购,用于运行服务器软件.1 本来是为了优化对于需要长时间运行的任务、大量内存和可扩展环境的大型应用程序,对这些场景的优化比 服务器模式(另见:java -server"和java -client"之间的真正区别?).
JRockit was originally developed by Appeal and BEA Systems before being acquired by Oracle to run server software.1 It was meant to be optimized for large applications requiring long running tasks, a lot of memory and a scalable environment, pushing optimizations for these scenarios even further than the Sun HotSpot JVM in server-mode (see also: Real differences between "java -server" and "java -client"?).
自甲骨文收购 Sun Microsystems 以来,甲骨文就具体计划和路线图进行了沟通JRockit 和 HotSpot JVM 融合成为两全其美"的实现,主要基于 HotSpot 构建,但集成了 JRockit 最流行的功能.
Since the acquisition of Sun Microsystems by Oracle, Oracle has communicated on a concrete plan and roadmap to have JRockit and the HotSpot JVM to converge to be a "best of both worlds" implementation, mostly built on HotSpot but integrating the most popular features of JRockit.
事实上,正如同一个博客所述,JRockit 不会作为 Java 发布7 虚拟机;并且 JRockit 的一些功能正在逐步引入 HotSpot (内部甚至有时现在称为HotRockit").
In fact, and as mentioned on the same blog, JRockit won't be released as a Java 7 JVM; and some of JRockit's features are being incrementally brought into HotSpot (internally even sometimes now referred to as "HotRockit").
更多详情,请阅读:
1 部分摘自 Wikipedia 于 2012 年 3 月 3 日美国东部标准时间下午 1.50.
1 As partially pulled from Wikipedia on March 3, 2012 at 1.50PM EST.
这篇关于JRockit JVM 与 HotSpot JVM的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!