Hello - I've observed a noticeable performance difference in looking up completions in a WFSTCompletionLookup when it is created using the build() method with a TermFreqIterator versus one that is created by loading a previously saved instance, with the instance created from the build method being faster. The saved lookup is ~275MB on disk. I have not dug in to determine why this is, but is this to be expected?
Thanks, Michael --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
