- This topic has 6 replies, 3 voices, and was last updated 18 years, 8 months ago by
.
-
Posts
-
Hello,
On my machine, JSP validation is extremely slow even for a small project. It seems the reason is that an external javac compiler is invoked for each file, which means a new Java VM is started up every time, making this feature unusable even for small projects.
Is there a remedy for this?
christian
Yes you are correct. How slow is too slow? Typical is 1-3 seconds, even with other JSP compilations in other IDES like IntelliJ. Have you tried adjusting your startup params like so: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-10087.html
JSP compilation in general is extremely expensive since it requires two compilation passes. The actual cost of spinning up the javac process is about 5% of the total processing time per file. In 4.1 we made a major optimization to the compilations of large projects where the entire build path was being recreated each time, so for big projects we saw improvements of compile time by up to 65%.
my VM settings are adjusted as described. For me, on a 1.5 Meg 2 MHz PIV, JSP compilation takes about 1-2 seconds per file. I am using ME 4.1.1, but I wouldnt want to try this on a large project
That sounds about right; I do agree that in the general case JSP validation/compilation is not a performant operation. We do have an open issue to further optimize it, I will add your comments to it to see if there is more work we can do in this area.
I’m not sure if it is relevant, but I recently had cause to do a checkout page where I had a few large drop downs for countries/codes and states/provinces. The editor never crashed on me, but it would take regular vacations, making it pretty painful to work with.
I later removed the country-list drop downs out of curiosity to see if this was contributing to my issues, and the editor picked up again. The drop downs did not contain any JSTL/Scriptlet code, just flat HTML.
