Hello Thomas, Thanks for your answer.
I'm using version 2.6.5 of jackrabbit. We're loading 300.000+ documents in production and it takes 3-5 minutes to load it all. 2 queries are run : the select * with a limit, and the select * without limit. I'll attach the source file source_jackrabbit.txt <http://jackrabbit.510166.n4.nabble.com/file/n4661929/source_jackrabbit.txt> In the development environment, i set the logging of jackrabbit to debug, and it appeared that the first query was taking a lot of time. However, setting the logging level to DEBUG seriously decreased the overall performance. I'll run another test without count and without debug mode on a large set of documents to be sure, thanks for the advice. By the way, i've heard of another implementation of QueryResult that would return the totalSize of the query without "limit" : org.apache.jackrabbit.core.query.lucene.QueryResultImpl. But org.apache.jackrabbit.core.query.lucene.QueryResult only works with SingleColumnQueryResult. -> Any idea how to use QueryResultImpl and if it is a viable solution ? Is jackrabbit able to properly handle queries on millions of documents as long as we have a limit in the query ? Kind Regards, Cédric -- View this message in context: http://jackrabbit.510166.n4.nabble.com/really-poor-search-performance-tp4661920p4661929.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
