JEP 145发生了什么(由于编译代码重用,jvm启动速度更快)? [英] What happened to JEP 145 (faster jvm startup due to compiled code reusage)?

查看:110
本文介绍了JEP 145发生了什么(由于编译代码重用,jvm启动速度更快)?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

2012年, JEP 145 已创建,以便
在java中缓存已编译的本机代码,用于更快的jvm初创公司

In 2012, a JEP 145 has been created in order to
cache compiled native code in java for faster jvm startups.

那时,它已经正式宣布。

然而, JEP 145不再存在

它发生了什么?这个想法听起来很棒。

我找不到官方声明为什么以及何时取消这个项目。

What happened to it? The idea sounds great.
I could not find an official statement why and when this project has been cancelled.

推荐答案

JEP的文本仍然可以在 JEP中找到源存储库

The text of the JEP is still available in the JEP source repository:

http:// hg .openjdk.java.net / jep / jeps / raw-file / c915dfb4117d / jep-145.md

似乎没有记录它被取消的原因。但我们现在知道 AOT正在开展工作并解决了许多相同的问题,可能是一种更容易实现和维护的方式。事实上,AOT JEP说:

There doesn't seem to be a documented reason for it to be canceled. But we now know that AOT is in the works and it solves many of the same problems, possibly in a way that's easier to implement and maintain. In fact, the AOT JEP says:


有可能保存一个非常晚的低级别IR副本,但这看起来并不复杂。

It is possible that saving a very late copy of the low-level IR could be done instead, but that seems no less complex.

这似乎解释了为什么145不可行。

That certainly seems like an explanation of why 145 is not the way to go.

这篇关于JEP 145发生了什么(由于编译代码重用,jvm启动速度更快)?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆