Here some preliminary results for the CPU time. Captured while the query was executing
Non-indexed query for XML-RPC CPU usage spends 97.92% at org.apache.xindice.server.rpc.messages.Query.execute() where 69.01% - org.apache.xindice.core.Collection.queryCollection() and 28.85% - org.apache.xindice.server.rpc.messages.Query.queryWrapper() Hot spots: 15.88% - 622 inv. org.apache.xindice.core.filter.BTree$BTreeNode.read() 10.35% - 652 inv. xml.dom.ElementImpl.loadAttributes() 5.58% - 153 inv. org.apache.catalina.loader.WebappClassLoader.findClassIntenal() Non-indexed, Embed CPU spends 39.996% at org.apacje.naming.resources.FileDirContext.file() where 21.06% - org.apache.catalina.startup.HostConfig.run() and 18.55% - org.apache.catalina.loader.WebappLoader.run() also spends 33.64% at java.net.PlainSocketImpl.accept() Nothing jumps out of the memory screen, just lots of chars[] and Strings processing -----Original Message----- From: STONE,ROBERT (HP-SanDiego,ex1) Sent: Friday, April 04, 2003 11:54 AM To: 'xindice-users@xml.apache.org' Subject: RE: xindice1.1b performance Thanks for the suggestions >> 1. try the embed driver: this will give you access to the "raw" Xindice >> performance, without any transport overhead (it might well be XML-RPC >> serialization/deserialization, though I seriously doubt it); Done. Same query, same source. Before indexing Embedded, - 93324 ms XML-RPC - 88843 ms After indexing Embedded, - 1683 ms XML-RPC - 1402 ms Same box, same code and RPC is faster? >> 2. check to see where most of the time is spent. I'd suspect something >> in Xalan code during the XPath search. I'm going to run it through the OptimizeIt, see where the time is spent and post the results Thanks, Bob Stone
