如果基本，示例 GWT 应用程序需要 30 秒才能在浏览器中加载，这正常吗?真正的应用程序需要 2 分钟吗? [英] if basic, sample GWT app takes 30sec to load in browser, is that normal? will real apps take 2 mins?

问题描述

我有一台能够运行 64 位 Windows 7 的不错的机器.那么为什么每次我在开发模式"下停止一个小示例 GWT 应用程序，编辑它并重新启动它需要 30 秒才能在浏览器中响应，在最新的 Firefox 和最新的 Chrome 中?

I have a decent machine capable of running 64 bit Windows 7. So how come any time I stop a small sample GWT app in "development mode", edit it and restart it it takes 30 sec to become responsive in the browser, both in latest Firefox and latest Chrome?

这种基于糖蜜的编辑-编译循环是否只是当今 GWT 开发人员所期望的正常现象?

Is that sort of molasses-based edit-compile cycle just the normal, expected thing for GWT developers nowadays?

对于更现实的应用程序，它会变得更糟，还是整个 30 秒只是框架开销，而我自己的代码不会让它在短时间内变得更加臃肿?

Will it get much worse for more realistic apps or is the whole of those 30 sec just the framework overhead, and my own code would not make it much more bloated than that any time soon?

能否通过使用其他模式"或任何其他调整解决方案来缓解此问题?

Can this problem be alleviated by using some other "mode" or by whatever other tweak solution?

Google 员工的机器是否比我的机器快得多，这样痛苦更小，还是他们像我们其他人一样受苦?

Do Google people have much faster machines than I do on which this is less of a pain or do they suffer like the rest of us?

推荐答案

我想我的回答是一个问题的形式，你确定你真的需要重启吗?"

I guess my answer is in the form of a question, "Are you sure you're really needing to restart at all?"

假设您在浏览器中运行它(听起来像您一样)，那么大多数更改几乎在您完成后就会热门".我昨天花了很多时间对模块中的主代码文件进行各种更改，并且不必为其中任何一个重新启动服务器.

Assuming you're running it hosted within the browser (which it sounds like you are) then most changes are "hot" almost as soon as you've finished them. I spent yesterday doing all kinds of changes to the main code file in a module and didn't have to restart the server for any of them.

我经常不得不在浏览器中重新加载页面才能看到更改，但这是一个不同的问题.

I often had to reload the page within the browser to see the changes, but that's a different issue.

这篇关于如果基本，示例 GWT 应用程序需要 30 秒才能在浏览器中加载，这正常吗?真正的应用程序需要 2 分钟吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！