DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33650>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33650 Summary: Jasper performance for multiple files processing Product: Tomcat 5 Version: 5.0.30 Platform: PC OS/Version: Windows XP Status: NEW Severity: enhancement Priority: P2 Component: Jasper AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Jasper performance is abysmal when using jspc to precompiles jsps, or more especially to generate the java files. I have a webapp with 450 jsps, jasper generates the java files in 12 minutes. In comparison, javac compilation for those 450 generated java files is performed in 1 minute. Profiling and debugging the code, it appears clearly that most of the time is spent doing the same parsing for static include directives over and over. Typically a page includes an init page which itself includes 2 init pages. page.jsp -> init.jsp -> { init-a.jsp, init-b.jsp, ... } For each and every page, the parser always go down the tree without caching includes and parse init.jsp, and so on. So basically the init.jsp is parsed 450 times. The Mark object is also pretty inefficient as it generates bazillions of objects which are not so lightweight (via Mark.mark()). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]