Re: Optimizing and XMLC application
Arno Schatz <[email protected]>
| Newsgroups | gmane.comp.java.enhydra.xmlc |
|---|---|
| Message-ID | <[email protected]> |
Hi David, I was faced with the same problem on my project. I could significantly reduce the replication tie by reducing the number of nodes by changing the HTML (basically your suggestion 1). Changing to LazyDOM for replications is about 10-20% slower, I measured on a 100 rows, 15 changes per row. (At the end we actually limited the output to 50) In regards to profiling: XMLC is creating a lot of objects in the cae of replication, causing garbage collection to eat up the time. The profilers I used do not seperate out the time for gc, the time for gc just appear in the time consumption of other methods. So the results are really inaccurate. -Arno David Corbin wrote: > 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. > > > _______________________________________________ > XMLC mailing list > [email protected] > http://www.enhydra.org/mailman/listinfo.cgi/xmlc >