Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Message-ID: <9074030.post@talk.nabble.com>
Date: Tue, 20 Feb 2007 17:34:56 -0800 (PST)
From: James Hang <jhang@bea.com>
To: users@jackrabbit.apache.org
Subject: Re: [JCR Browser] NodeIterator very slow
In-Reply-To: <227621ad0702020538k251b9850r8786917acf2afe43@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <227621ad0702020538k251b9850r8786917acf2afe43@mail.gmail.com>


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#a9074030
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.