DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22090>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22090 EL evaluation should cache parse results ------- Additional Comments From [EMAIL PROTECTED] 2003-08-04 09:24 ------- Evidence (threaddumps) supports that the problem is not the parsing performance per se, but the allocation of three (8k+16k+16k) buffers per parser invocation: SimpleCharStream.java: #245: buffer = new char[buffersize]; #246: bufline = new int[buffersize]; #247: bufcolumn = new int[buffersize]; "tcpConnection-8001-14" daemon prio=1 tid=0x4e102df8 nid=0x33ca waiting for monitor entry [bbdfe000..bbdff908] at org.apache.commons.el.parser.SimpleCharStream.<init>(SimpleCharStream.java:245) at org.apache.commons.el.parser.SimpleCharStream.<init>(SimpleCharStream.java:253) at org.apache.commons.el.parser.ELParser.<init>(ELParser.java:1721) This is kind of a commons/el problem, not a jasper one. I will try to patch el to use smaller buffers (which expression is 4k???). If that improves matters, I might close this report although I still consider it valid. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
