COuld you please give us your bench with a brand new version of the sitemap.xmap (for example, edit it, change a line, save the file, measure the perf with a given processor, and reprocess all that for each processor).
On a slow 128MB machine, sitemap compilation takes ages to complete. TreeProcessor is much faster. I did not try with Saxon. Graaf, Edgar de (fin) wrote: > Hi, > > Recently I installed the TreeProcessor instead of compiling. Everyone says > it is faster then compiling the sitemap, so I didn't test it. Then I > installed Saxon and tot test Saxon I did a Jmeter test. My application > collapsed from 6 seconds average response time to 20 seconds!? So I put > xalan back, 27 seconds!? Then I put the compiled version back and I got 6 > seconds.... my question to you is: > > Does anybody know why this could be? Does the TreeProcessor cost more > memory? (I only have 196 MB) Are there some bugs in certain versions of the > TreeProcessor? Or is the TreeProcessor just not scaleable? > > Thanks, > > Edgar > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
