java 和 java 之间的区别和“libjvm.so” (Linux) 或“jvm.dll” （视窗）？
通过普通 java 命令启动应用程序与通过 Linux 中的 libjvm.so 或 Windows 中的 jvm.dll 直接调用 JVM 有什么区别？
最近我在论坛上看到使用dll或.so文件启动eclipse会提供更好的性能。我想了解这是如何发生的。
谢谢。
What are the differences in starting an application through the plain java command, against directly invoking the JVM through libjvm.so in Linux or jvm.dll in Windows ?
Recently I saw on a forum that starting eclipse using the dll or .so file will give better performance. I would like to get to know how this happens.
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
通常，如果人们想要将自己的功能包装在 Java 核心周围，那么他们会针对 jvm.dll 进行构建，有时很难做一些看起来像 Java 的“本机”的事情。 Eclipse 确实是一个很好的例子，他们希望在启动之前弹出一个启动屏幕并执行一些其他操作。对于其他产品，Java 只是其工作负载的一小部分（例如：大型 C++ 应用程序需要在某些时候桥接到 Java）。
从性能角度来看，这是无关紧要的。这完全取决于您希望如何“适合和完成”诸如 Eclipse 之类的东西。
Typically folks build against jvm.dll if they want to wrap their own functionality around a Java core, where sometimes it's hard to do things that look "native" from Java. A good example is indeed Eclipse, where they want to pop up a splash screen and do some other actions before starting up. For other products, it's that Java is only a small part of their workload (eg: large C++ app that needs to bridge into Java at some point).
From a performance perspective, it's irrelevant. It's all about how you want the "fit and finish" for things like Eclipse.
链接讨论了 Eclipse 启动；这可能会更快，因为通过使用
-vm参数来指定 JRE，Eclipse 可执行文件不必在系统中搜索合适的 JRE 来启动（这会导致磁盘 I/O，并且可能会导致涉及检测版本JRE）。你不是在加速 Java，而是在加速 本机启动器。The link discusses Eclipse start-up; it is likely that this is faster because, by using the
-vmargument to specify the JRE, the Eclipse executable doesn't have to search the system for an appropriate JRE to launch (which would incur disk I/O and possibly involve detecting the version of the JRE). You aren't speeding up Java, you're speeding up the native launcher.