ProGuard 性能 - ProGuard 会让我的软件更快吗？
有没有人有使用 ProGuard 的经验，并且是否已经有关于类加载时间之外的应用程序性能的测量？
我有一个相当复杂的应用程序，可能需要增强，但为 ProGuard 准备它需要几天时间，所以我想先听听一些意见。
Does anyone have experience in using ProGuard and are there already measurements about application performance beyond the class loading time?
I have a fairly complex application that could need a boost, but preparing it for ProGuard would take a few days, so I would like to hear some opinions before.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
ProGuard 所做的大多数字节码优化都可以通过任何主流 JVM 的 JIT 完成，甚至更好，因此对于那些您不应该期望显着的改进（类加载除外）。
Most of the bytecode optimizations that ProGuard does are done just as well or better by any mainstream JVM's JIT, so for those you shouldn't expect significant improvements (except for class loading).
根据我们的经验，主要好处是它可以保护您的知识产权。就类加载时间而言，我们不一定看到任何好处，即使有，也可以忽略不计。
另一件事是我们已经看到了可能对您的代码产生负面影响的问题。当然，使用 ProGuard 后重新测试您的应用程序。
The main benefit, from our experience, is that it can protect your intellectual rights. In terms of class loading time, we are not necessarily seeing any benefit and if so is negligible.
One other thing is we have seen issues where it can affect your code negatively. Certainly, retest your application after using ProGuard.
我只能胡乱猜测。
优点：混淆且较短的方法名称/字段名称使其在字节代码验证、类加载和解释模式中稍快一些。
缺点：一旦运行一段时间，它就会或多或少地进行 jit 编译，到那时它就不再重要了。
I can only make a wild guess.
Pro: obfuscated and shorter method names / field names make it slightly faster in byte code validation, class loading and interpreted mode.
Cons: as soon as it is running a while it will be more or less jit compiled and at that point it won't matter any more.