Grails 1.0 到 1.3 - 速度提升？
我试图证明 Grails 从 1.0 升级到 1.3 的合理性，并且想知道是否可以增加速度的好处。有人有关于这个主题的经验数据吗？
I am trying to justify an upgrade of Grails from 1.0 to 1.3 and am wondering if I can add speed to the benefits. Does anyone have any empirical data on the subject?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
当然，这取决于很多事情，而且您还没有分享您的申请的很多细节。如果您使用的是 1.0.3 或更早版本，默认情况下是急切加载集合，并且此错误已在 1.0.4 中修复，因此在处理您希望延迟加载的集合时，升级到 1.3 肯定会更快。 1.1、1.2 和 1.3 中的 GSP 渲染性能也有了显着提升。此外，GSP 现在在构建 war 文件时进行预编译，因此部署的应用程序使用的 permgen 少得多。
从 1.0 中使用的 1.5.x 到 1.3.7 中使用的 1.7.8，Groovy 的速度也快了很多。
还有其他与性能无关的升级原因。其中包括访问 1.0 中不存在的新功能、在旧版本中无法使用的插件以及更好的 IDE 支持。
It depends on a lot of things of course, and you haven't shared many details of your application. If you're using 1.0.3 or earlier, the default was to eagerly load collections and this bug was fixed in 1.0.4, so upgrading to 1.3 will certainly be faster when working with collections that you expect to be lazy-loaded. There have also been significant performance increases in GSP rendering in 1.1, 1.2, and 1.3. In addition GSPs are now precompiled when building a war file, so deployed applications use a lot less permgen.
Groovy has also gotten a lot faster from the 1.5.x that was used in 1.0 to the 1.7.8 that's used in 1.3.7.
There are other non-performance-related reasons to upgrade too. These include access to newer features that didn't exist in 1.0, plugins that won't work in older versions, and better IDE support.
这是一个巨大的飞跃，我不确定您会看到多少性能优势，但确定性很大。但是，您应该考虑升级的其他优势 - 错误修复、新功能、更简单的 gorm 查询、能够使用最新的插件等。
仅供参考：我们确实从 1.* 升级到 1.3，并且需要进行一些代码更改。虽然不多，但可以将其视为清理和减少代码数量的机会。
That's a big jump and I don't for sure how much performance benefit you will see but it's certainty a lot. However, you should consider other advantages for the upgrade -- bug fixes, new features, easier gorm query, able to use latest plugins, etc.
FYI: We did upgrade from 1.* to 1.3, and it's requires some code change. Not a lot but take it as opportunity to clean and cut down on code count.