[
https://issues.apache.org/jira/browse/LUCENE-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015981#comment-16015981
]
David Smiley commented on LUCENE-7834:
--------------------------------------
bq. But then you pay the price at query time since the FST needs to be loaded
as part of query execution. This doesn't sound like a better default to me, it
is just moving the problem?
It's ultimately a trade-off that the user can be in control of through the
amount of warming they do. I don't view this as "moving the problem"; perhaps
we aren't thinking of "the problem" as the same thing. The "problem" I'm trying
to solve is to save memory/latency _that sometimes won't even be needed at all_.
> BlockTree's terms index should be loaded into memory lazily
> -----------------------------------------------------------
>
> Key: LUCENE-7834
> URL: https://issues.apache.org/jira/browse/LUCENE-7834
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/codecs
> Reporter: David Smiley
> Assignee: David Smiley
> Attachments: LUCENE_7834_BlockTreeLazyFST.patch
>
>
> I propose that BlockTree delay loading the FST prefix terms index into memory
> until {{terms(String)}} is first called. This seems like how it should work
> since if someone wants to eager load then they can use {{IndexReaderWarmer}}.
> By making the FST lazy load, we can be more NRT friendly (if some fields are
> rarely used), and also save memory (if some fields are rarely used).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
