Thanks again, Shawn.
You are completely right about the use of disk cache and the special note
regarding the optimize operation in Solr wiki.
This is not the cause of the problem though. The disk cache is important for
queries and overall performance during optimization, but once it is done,
everything should go back to "normal" (whatever that normal is). In our case
it is the SOFT COMMIT (that opens a new Searcher) that takes 10 times longer
AFTER the index was optimized and deleted records were removed (and index
size went down to 60 GB).
View this message in context:
Sent from the Solr - User mailing list archive at Nabble.com.