To further clarify, although we're only iterating over 100 nodes, each node has 5-10 child nodes, with 5-10 properties each. On each iteration, we are traversing the child node hierarchy of the node and all of their properties. This causes the following CacheManager messages to be printed continuosly:
2007-02-20 09:56:14,330 INFO CacheManager - resizeAll size=6 2007-02-20 09:56:15,384 INFO CacheManager - resizeAll size=6 2007-02-20 09:56:16,429 INFO CacheManager - resizeAll size=6 2007-02-20 09:56:17,616 INFO CacheManager - resizeAll size=6 .. .. Is there possibly an issue with the CacheManager when trying to access a large set of items (nodes and properties)? James James Hang wrote: > > Hi, > > Have you been able to find a solution for this problem? I think we are > having a similar issue on our end and we're actually dealing with a much > smaller result set - only 100 elements. The query appears to execute > almost instantly, but it takes a long time to iterate through the results. > > We tried setting the "respectDocumentOrder" parameter to "false" in the > SearchIndex configuration like someone suggested, but it didn't seem to > speed things up. > > Any help would be greatly appreciated! > > Thanks, > James > > > > Sridhar Raman wrote: >> >> I have a NodeIterator variable iter with 2000 elements. When I do an >> iter.hasNext() or an iter.next(), the program takes a very long time to >> execute the call. >> >> Is there any solution? I am not using jackrabbit 1.2.1 yet. Should I? >> Would >> it help? >> >> Thanks, >> Sridhar >> >> > > -- View this message in context: http://www.nabble.com/NodeIterator-very-slow-tf3160898.html#a9075695 Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
