[
https://issues.apache.org/jira/browse/LUCENE-9286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17064405#comment-17064405
]
Michael Sokolov commented on LUCENE-9286:
-----------------------------------------
I think we mostly looked at the size of the resulting FST and I don't believe
we paid much attention to the in-memory FST, does that seem right [~broustant]?
The in-memory is expected to be bigger because pointers, tails are not yet
shared, etc, but that seems like a big difference (50MB vs 8GB). [~dweiss] one
thing to try as a sanity check is to set
FstCompiler.Builder.directAddressingMaxOversizingFactor(-1) - that should
disable the direct addressing and the bit tables it uses should not be
allocated.
> FST construction explodes memory in BitTable
> --------------------------------------------
>
> Key: LUCENE-9286
> URL: https://issues.apache.org/jira/browse/LUCENE-9286
> Project: Lucene - Core
> Issue Type: Bug
> Affects Versions: 8.5
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Major
> Attachments: screen-[1].png
>
>
> I see a dramatic increase in the amount of memory required for construction
> of (arguably large) automata. It currently OOMs with 8GB of memory consumed
> for bit tables. I am pretty sure this didn't require so much memory before
> (the automaton is ~50MB after construction).
> Something bad happened in between. Thoughts, [~broustant], [~sokolov]?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
