[jira] Updated: (LUCENE-2773) Don't create compound file for large segments by default

["Michael McCandless (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LUCENE-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael McCandless updated LUCENE-2773:
---------------------------------------

    Attachment: LUCENE-2773.patch

Patch.

I added a get/setNoCFSRatio to LogMergePolicy, defaulted to 10% (0.1)
meaning if the estimated size of the merged segment is greater than
10% of the total size of the index, then we leave the merge segment in
non-compound format.

I also defaulted the maxMergeMB to 2 GB, meaning (w/ the default
mergeFactor of 10) your biggest segments will be 2 - 20 GB.


> Don't create compound file for large segments by default
> --------------------------------------------------------
>
>                 Key: LUCENE-2773
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2773
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 3.1, 4.0
>
>         Attachments: LUCENE-2773.patch
>
>
> Spinoff from LUCENE-2762.
> CFS is useful for keeping the open file count down.  But, it costs
> some added time during indexing to build, and also ties up temporary
> disk space, causing eg a large spike on the final merge of an
> optimize.
> Since MergePolicy dictates which segments should be CFS, we can
> change it to only build CFS for "smallish" merges.
> I think we should also set a maxMergeMB by default so that very large
> merges aren't done.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org