How often to call commit on an offline Solr/Lucene index? -
i know there have been semi-similar questions, in case, building index offline, until build complete. building scratch 2 cores, 1 has 300k records alot of citation information , large blocks of full text (this document index) , core has 6.6 million records, full text (this page index).
given index being built offline, real performance issue speed of building. noone should querying data.
the auto-commit apparently fire if stop adding items 50 seconds? don't do. adding ten @ time , added every couple seconds.
so, should commit more often? feel longer runs slower gets, @ least in test case of 6k documents index.
with noone searching index, how suggest commit?
should using solr 3.1 , solrnet.
although it's commits taking time you, might want consider looking other tweaking commit frequency.
is indexing core searching, or replicated somewhere else after indexing concludes? if latter case, turning off caches might have noticeable impact on performance (solr rebuilds caches every time commit).
Comments
Post a Comment