logo       

Optimizing and XMLC application: msg#00053

java.enhydra.xmlc

Subject: Optimizing and XMLC application

I have an XMLC-based application that needs some optimiztion. It is XHTML
based (which, I think means it cannot use the LazyDOM, right?).
Even so, the primary page I need to optimize (at this point) duplicates
and populates a block of about 8-10 elements. The problem is when we do
that 300 times, on one page we get a little slow. I'm looking for
optimzation tips. Small localized optimizations are most desired, but
I'll certainly consider larger-scale ones (see below). Here are some that
have occurred to me:
1) Eliminate all the "white-space-text nodes" that are not really
necessary in the duplicated "row" template2) Consider converting to HTML and
using LazyDOM (will this really help me
if I'm mostly creating new nodes?3) Pre-generate large chunks of the final DOM
(a good majority of the
duplicated "rows" are from domain data, and fairly static).4) Pre-generate the
data has HTML at run-time, or even at compile time
(see #3 above)5) Look for minor optimizations that can be done to XMLC or
Xerces itself.
6) Find a better XML/XHTML Dom implementation than Xerces uses.

Please help.
Thanks.
David Corbin

P.S. I am doing profiling and looking for "hot spots", but as near as I
can tell (it's still early) there are no GOOD java profilers.


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise