Eclipse Webtools项目（WTP）及其性能/质量 [英] Eclipse webtools project (WTP) and its performance / quality
问题描述
我目前正在使用WTP 3.2评估 eclipse 3.6.2 .3 应该用WTP 3.0.4替代eclipse 3.4.2作为我们的主要IDE。
我不得不说，对表现感到失望：
WTP 3.2.3似乎比3.0.4慢得多。
事实上我真的很想知道为什么WTP每个版本都会慢一些。
我们的一个应用程序（动态Web项目）包含大约4000个java类和700个jsps / jsp片段即可。我们只需要基本的WTP功能来开发jsps，xmls和xsd。我们不需要像 Dali 这样的高级复杂功能（JPA工具真的被一个 webtools项目覆盖） em>？），天秤座或 visual xml编辑器在第一位。
另一个有趣的一点是，WTP似乎减慢整个IDE < STRONG>。
SWT是非常重要的几秒钟，cpu的使用非常高（特别是在构建完成后 - 如果你看系统作业，几个jsp / javascript索引器正在工作几分钟，即使所有WTP构建验证程序已禁用），打开新文件较慢，导航项目等。
这可以在仅包含单个核心cpu。
最糟糕的是，我有一种感觉，WTP开发团队不关心性能
（例如，查看 http://wiki.eclipse.org/WTP_Performance_Tests 页面 - 上次更新于2008年进行）
有关基本功能（例如jsp编辑/验证）性能的错误报告和新闻组帖子经过一段时间后会被忽略或关闭，例如：此处，此处，和这里。
请不要误会我的问题：
我不想WTP。
其实我相信WTP是一个由有才华的团队开发的一个很好的开源项目。
但显然，项目的质量保证有问题，特别是在影响可用性和用户接受度的性能方面。
我只想指出，团队应该专注于对于大多数用户来说，这是至关重要的，而之后就是实施超级重复功能。
我的问题
- 什么你是否有WTP的经验，特别是最新的版本？
- 你可以确认还是反驳我的意见？
- 有更好的选择吗？ >
- 您是否从WTP切换到WTP，为什么？
- 您是否有一些最佳做法来加快速度，尤其是像我们这样的中高档
更新
我想对此问题进行更新，以反映当前的答案和
来总结当前的结果：
-
许多用户或多或少地抱怨相同的问题，所以我看到这些问题被确认。
BTW，这个问题也在一个新闻文章中提到 theserverside.com 附加评论。 -
负责任的WTP项目负责人，对我们现在的WTP的情况做出了突出的贡献，我喜欢引用： br>
简单的事实是，我们不会花费太多时间进行性能测试，因为我们缺乏这样做的资源。
当然，我们想要积极主动，而不是被动，但我们倾向于把时间分配给功能问题。
所以这个问题会变成一些公开信给社区的WTP团队：
亲爱的WTP团队，
很明显，WTP正在遭受重大质量/性能问题
你试图放下或忽略。
请投入一些时间来改善目前的情况
，以新增功能为代价，并且为了解决目前的问题，做一切所需要的
。
例如恢复绩效团队，在
以前的版本之间进行一些回归测试，或询问社区（精确定义）帮助。
我相信他们有足够的人愿意并能够在这里帮忙。
如果你喜欢，做一些民意调查，以获得一个感觉，应该是
是未来WTP版本的最重要的范围。
请，请听你的社区。
为了回应，我是项目的主角在WTP中提供JSP，XML和JavaScript源编辑功能。简单的事实是，我们不会花太多时间进行性能测试，因为我们缺乏这样做的资源。当然，我们希望主动，而不是被动，但我们倾向于把时间分配给功能问题。我们确实有一个采用产品定期运行性能回归测试的方法，但是我预计现在测试是在多核机器上运行的 - 而且我们还没有任何新的红旗报告给我们一段时间。
在您链接到的3个错误中，2在3.0.4版本之前，您称赞，第三个是格式化性能问题（自定址）或一个具有同类型验证特定到XML文件（其修复将会引发Xerces，iirc中的内存泄漏，因此我们不会在那时进行内存泄漏）。如果你有具体的项目，你可以附加到一个错误，并说做X在3.2减少Y量，我们将做我们可以找出哪里有一个回归。
对于索引器，他们至少应该完成。存储的磁盘信息在WTP版本之间已更改，并且这些文件需要重新处理，以便它们再次包含在搜索和（实现）重构操作中）。一旦初始索引完成，它应该逐渐执行，几乎不明显。您可能遇到的一个体系结构变化是，对于JSP，整个工作区需要在该索引的单个工作台会话中进行索引，以被认为是最新的。关闭Eclipse不受挫折只会延长后处理的影响。
这听起来像是您公司的标准安装包括整个WTP而不是滚动自己的定制分发。我敦促您检查启动和关闭首选项页面，并关闭早期启动任何不感兴趣的功能。没有你提到兴趣使用这个设施，但还有其他领域的WTP和平台。您无法验证的任何内容都是在验证首选项页面上的公平游戏，以及默认情况下在 Web上验证JSP片段的设置 / JSP文件 / 验证首选项页面。
Our company is using eclipse since several years now (we are using WTP since release 0.7)
I am currently evaluating eclipse 3.6.2 with WTP 3.2.3 which should replace eclipse 3.4.2 with WTP 3.0.4 as being our main IDE.
And I have to say that once again I am quite disappointed in concerns of performance:
WTP 3.2.3 seems to be much slower than 3.0.4.
In fact I am really wondering why WTP gets slower with each release.
One of our applications (dynamic web project) contain about 4000 java classes and 700 jsps/jsp fragments. We only need basic WTP functionality for developing jsps, xmls and xsd. We don't need high sophistic features like Dali (should JPA tools really covered by a webtools project?), Libra or a visual xml editor in the first place.
Another interesting point is that WTP seems to slow down the whole IDE. SWT is non-reponsive for some fraction of seconds, cpu usage is very high (especially after a built took place - if you look at the system jobs, several jsp/javascript indexers are doing work for some minutes, even if all WTP build validators have been disabled), opening new files are slower, navigating through the project etc.
This can be especially seen on older machines which do contains only a single core cpu.
The worst thing is that I've got the feeling that the WTP dev team does not care much about performance (e.g. have a look at the http://wiki.eclipse.org/WTP_Performance_Tests page - last update took place in 2008).
Bug reports and Newsgroup posts regarding to performance of basic features (e.g. jsp editing/validating) are often ignored or closed after some time, some examples: here, here, and here.
Please don't get me wrong:
I don't want to blame WTP.
In fact I believe that WTP is a good open-source project developed by a talented team.
But obviously the project has a problem with its quality assurance, especially in terms of performance which affects usability and user acceptance.
I just want to point out that the team should focus on the things which are essential to most of the users in the first place and afterwards work on implementing super-duper-features.
My Questions
- What are your experiences with WTP, especially the most recent releases?
- Can you confirm or disprove my observations?
- Are there better alternatives?
- Did you switch from or to WTP and why?
- Do you have some best practices to speed it up, especially for upper-mid-sized like ours?
UPDATE
I'd like to make an update on this question to reflect the current answers and to sum up the current results:
Many users complain about more or less on the same issues so I see those issues as confirmed.
BTW, this question is also mentioned on a news post on theserverside.com with additional comments.The responsible WTP project lead, nitind, made a notable post on the current situation of WTP, which I like to cite:
"The simple fact is that we don't spend much time on performance tests because we lack resources for doing that."
"Of course we'd like to be proactive about it rather than reactive, but we tend to allocate our time to functional problems first."
So this question turns a little bit into some kind of an open letter from the community to the WTP team:
Dear WTP team,
it's obvious that WTP is suffering from major quality/performance issues
which you try to play down or to ignore.
Please invest some time to improve the current situation
at the cost of new features and do everything what's required
to solve the current problems.
E.g. revive the performance team, do some regression tests between
previous releases or ask the community for (precise defined) help.
I am sure that they are enough people willing and able to help here.
If you like, do some kind of poll to get a feeling what should be
the most important scopes of future's WTP releases.
Please, please, listen to your community.
To respond, I'm the lead for the projects that supply the JSP, XML, and JavaScript source editing functionality in WTP. The simple fact is that we don't spend much time on performance tests because we lack resources for doing that. Of course we'd like to be proactive about it rather than reactive, but we tend to allocate our time to functional problems first. We do have an adopter product running performance regression tests regularly, but I expect that tests are run on multi-core machines by now--and we haven't had any new red flags reported to us for some time.
Of the 3 bugs you linked to, 2 predate the 3.0.4 version you laud and the third is either a formatting performance issue (since addressed) or one with as-you-type validation specific to XML files (the fixing of which would have triggered a memory leak in Xerces, iirc, hence us not putting it in at that time). If you have concrete projects that you can attach to a bug and say "doing X is slower in 3.2 by Y amount", we'll do what we can to figure out where there's a regression.
As for the indexers, they should at least eventually complete. The on-disk information that is stored has changed between WTP versions, and those files need to be reprocessed so they're again included in search and (where implemented) refactoring operations. Once the initial indexing is complete, it should act incrementally and be virtually unnoticeable. One architectural change you may be running into is that for JSPs, the entire workspace needs to be indexed in a single workbench session for that index to be considered "up to date". Shutting down Eclipse out of frustration will only prolong the impact of that reprocessing.
It sounds like your company's standard install includes the entirety of WTP rather than rolling your own custom distribution. I urge you to check the Startup and Shutdown preference page and turn off early startup of any functionality you're not interested in using. Nothing you've mentioned interest in makes use of that facility, but there are other areas of WTP and the Platform that do. Anything you're not interested in validating is fair game on the Validation preference page, as well as the setting to validate JSP fragments by default on the Web / JSP Files / Validation preference page.
这篇关于Eclipse Webtools项目（WTP）及其性能/质量的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
