[
https://issues.apache.org/jira/browse/LUCENE-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17538194#comment-17538194
]
Robert Muir commented on LUCENE-10574:
--------------------------------------
I think another approach is to actually remove the {{O(n)^2}}, remove
{{floorSegmentBytes}}, let it kick into all the benchmarks. Now that the bad
algorithm is gone, followup by looking at alternative, safe methods to try to
keep the number of segments "contained" that don't cause pathological
performance issues.
It seems we all just accept this {{O(n)^2}} as a necessity, but I really don't
know why: I'm not sold on it at all.
> Remove O(n^2) from TieredMergePolicy or change defaults to one that doesn't
> do this
> -----------------------------------------------------------------------------------
>
> Key: LUCENE-10574
> URL: https://issues.apache.org/jira/browse/LUCENE-10574
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Priority: Major
>
> Remove {{floorSegmentBytes}} parameter, or change lucene's default to a merge
> policy that doesn't merge in an O(n^2) way.
> I have the feeling it might have to be the latter, as folks seem really wed
> to this crazy O(n^2) behavior.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
