[
https://issues.apache.org/jira/browse/LUCENE-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915094#comment-13915094
]
Robert Muir commented on LUCENE-5468:
-------------------------------------
{quote}
I'm not sure it matters here, but do you handle the FST Builder returning
null for the built FST (when there was nothing added)? Just a common
gotchya...
Do you have any sense of how the lookup speed changed?
{quote}
Many dictionaries have either no prefixes or no suffixes: the code comment
below this also answers your other question about NULL FST I think.
Admittedly its probably no faster now, but it can be faster if we make the
Stemmer smarter when walking the possibilities in the word:
{code}
// TODO: this is pretty stupid, considering how the stemming algorithm works
// we can speed it up to be significantly faster!
IntsRef lookupAffix(FST<IntsRef> fst, char word[], int offset, int length) {
if (fst == null) {
return null;
}
{code}
Given the fact this thing takes sometimes 100MB per field and makes it nearly
unusable, I made such larger changes a TODO for a separate issue?
> Hunspell very high memory use when loading dictionary
> -----------------------------------------------------
>
> Key: LUCENE-5468
> URL: https://issues.apache.org/jira/browse/LUCENE-5468
> Project: Lucene - Core
> Issue Type: Bug
> Affects Versions: 3.5
> Reporter: Maciej Lisiewski
> Priority: Minor
> Attachments: LUCENE-5468.patch, patch.txt
>
>
> Hunspell stemmer requires gigantic (for the task) amounts of memory to load
> dictionary/rules files.
> For example loading a 4.5 MB polish dictionary (with empty index!) will cause
> whole core to crash with various out of memory errors unless you set max heap
> size close to 2GB or more.
> By comparison Stempel using the same dictionary file works just fine with 1/8
> of that (and possibly lower values as well).
> Sample error log entries:
> http://pastebin.com/fSrdd5W1
> http://pastebin.com/Lmi0re7Z
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
