Hi, > Since the Lucene index is in any case updated asynchronously, it > should be fine for us to ignore the base NodeState of the current > session and instead use an IndexSearcher based on the last state as > updated by the async indexer. This would allow us to reuse the > IndexSearcher over multiple queries.
I was also wondering if it makes sense to share it across multiple sessions performing a query to reduce the number of index readers that may be open at the same time. however, this will likely also reduce concurrency because we synchronize access to a single session. we should also try to re-open the existing reader, which is less costly than creating a new reader. I'm not familiar anymore with the most recent lucene version, but with the version used in Jackrabbit 2.x this was possible and helped a lot. Regards Marcel
