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 danz8086@hotmail.com
 designates 65.54.246.98 as permitted sender)
Message-ID: <BAY103-DAV13B11F147B2335E2AF16BFD8DA0@phx.gbl>
From: "dan" <danz8086@hotmail.com>
To: <users@jackrabbit.apache.org>
Subject: RE: RowIterator loop is slow?
Date: Fri, 1 Dec 2006 09:54:10 -0500
Message-ID: <000001c71558$8f12d570$6a05140a@pointalliance.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <456FEF0B.2080000@gmx.net>
Thread-Index: AccVJ0NHlBIJeZpSSQaFcee7t1ffxQAKpcYg

Thanks Marcel,

> if your query does not have an 'order by' clause AND the query handler 
> configuration uses the default value for the
> 'respectDocumentOrder' parameter. In that case there is a post processing
> in the query result which orders the result nodes in document order.

That explains why it was slow for me - I have "order by @my:propname" in the
query, although I've already set "respectDocumentOrder" to false.

Now I feel somewhat agree with the idea in theads a few days back, about
"expanding RDB schema" and "if using RDB repository, let RDB do all
queries". 

IMO, "order by NOT_JUST_jcr:score" is very common use case. The way that
retrieving all nodes from multiple BLOBs into Java objects and then do Java
sorting, won't have any performance advantage over that allowing RDB to
handle everything in one shot. 
Also, many RDB products now have full-text search capability, although they
may not be as great as Lucene. When considering the 'over-all' performance,
it might be legitimate to think about a "RDB oriented search/query
mechanism". 

Of course, that may fall beyond the scope of Jacarabbit, as a reference impl
of JCR.

Thanks again & 
Best regards,
Dan