I've always thought that debugging didn't have much of an effect on the
performance of a TAF. I always knew that lots of debugging information
caused a lot of extra traffic to be sent back in the http response, and
I understood that pages may take longer to load when you have the
addition of many many kilobytes of text added to the resulting webpage,
but i ran into something here today that showed me there is more to it.
I wrote a java bean to essentially mirror the functionality of the @XSLT
tag but using the newest version of Xalan-J instead of the Xalan-C
included with Witango. I'm doing this to benefit form features that re
in Xalan-J that are not part of Xalan-C.
I have a page that sends a very large XML document to that bean to be
processed by a stylesheet. The page was taking a long time to load and
the last timestamp in the debugging output was always over 10000. Each
time the XSL processing bean was called, the input and ouput xml was
being included in the debugging information, and it was looking to me
like the xsl processing was taking up all the time. However when i
turned off debugging, i noticed the page loaded much quicker and the
time it took to execute on the server was on the order of 1-2 seconds
instead of 10-20.
Witango was really chewing up CPU simply writing those very large XML
results to the debugging output.
Anybody else ever run into the same thing?
--
John McGowan
[EMAIL PROTECTED]
P 847.608.6900 x 110
F 847.608.9501
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
