I suggest putting autoCommit at something as big as your memory allows
(eg 15 minutes) to flush the update log to disk and start merging
segments, but not yet visible on the search.
Then at the end, send an explicit wich will both persist on
disk the remainder of indexed docs and make everything
On Tue, Nov 12, 2013 at 9:56 PM, Eric Katherman wrote:
> Stats:
> default config for 4.3.1 on a high memory AWS instance using jetty.
> Two collections each with less than 700k docs per collection.
>
> We seem to hit some performance lags when doing large commits. Our front end
> service allows
