I don't think it will help; for instance SegmentReader of Lucene:
public synchronized Document document(int n, FieldSelector fieldSelector) Unsynchronized (in future) SOLR caching should help. -Fuad
I know this isn't really the place for this, so please forgive me - but does this patch look reasonably safe to use to skip the isDeleted check inside of FunctionQuery? My reasoning behind this is that many people (us included) will be building the index on a separate server, and then using the replication scripts to publish the files out to several read-only servers. On those instances, deletedDocs would always be empty, since it's a read only instance - and so we can conveniently skip the Lucene code in question. This flag would also be good for other optimizations that can only be made when you assume the index is read-only. Solr seems to work with the flag set - any reasons why this will crash and/or kill my kitten? (please forgive my posting this here instead of in solr-dev!) Index: src/java/org/apache/solr/search/FunctionQParser.java
...
