In your reply, you have mentioned that we use order by, did you mean 'order by @jcr:score' . Since I plan to permanently disable document order, I thought I will just add the entry
to both repository.xml and workspace.xml. I thought that should be sufficient. pkrishna wrote: > > I have been testing the performance of the following XPATH query > > String query = "//element(*, " + > JackRabbitNodeDefinitions.FROZEN_NODE.getNodeValue() > + ")[" + getXPathQuery(ctx, metadata) + "]"; > > where method getXPathQuery translates to a certain set of attributes. We > have 2 configurations pointed to by two different repository.xmls. One of > them points to a local database (database on the samebox where the test is > executing) and another one a remote database. When I test against a local > database I am able to retrieve more than 2000 nodes within 300~500ms. But > when I test against a remote database the same query takes about 7000ms to > retrieve 4 nodes. I do agree there could a some network latency but the > difference in times seems to reflect some other issues. Here are the > parameters we use for SearchIndex (repository.xml): > > <SearchIndex > class="org.apache.jackrabbit.core.query.lucene.SearchIndex"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > <!-- --> > > > > > > > > > > </SearchIndex> > > Any ideas\help on the cause of this problem would be appreciated. > > -- View this message in context: http://www.nabble.com/XPath-query-against-a-remote-database-is-very-slow-tp22995690p23061753.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
