|[wtp-dev] OOME and performance issues in JSDT - questions for those who use...|
I'd like to ask several questions regarding OOME while parsing/infer types issues and the overall performance...
There are pretty many related issues in bugzilla like the following:
Bug 323283 - [performance] Opening env.rhino.1.2.js hangs Eclipse
and many others...
These issues aren't easy to fix and mostly require to have some compromise between the performance and functionality.
- No warnings/error markers and/or annotations
- No outline/type hierarchy/override indicators.
- No more OOME errors
- (in future) Custom validators/content assist providers allowed.
This could really help with performance on big projects especially when JSDT doesn't plays the main role in project development.
Users may test such an option by replacing they JSDT from WTP M7 by the version built from my playground here:
Use the following command to build:
mvn clean install -DskipTests=true -Pbuild-individual-bundles
Then install from local site <YourProjects>/webtools.jsdt/site/target/repository/ directory (available after successful build).
BTW, having such option could be really useful if you're using a product like tern.java and angularjs-eclipse - they're provide ECMA5 compatibility and work a really faster this way.
And as no parsing/validation/content assist and so on is available when "External Builder/Validator" option is selected, I'd like to ask users what features they are really need and use in JSDT?
Regarding the performance issues listed, I strongly see one candidate to cut out from JSDT: It's override indicators that are doubling the performance glitches and adds almost nothing useful for users (imho). Should we cut it out?
What do you think?
Thanks in advance,
Back to the top