[
https://issues.apache.org/jira/browse/OPENNLP-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Wiesner updated OPENNLP-1903:
------------------------------------
Summary: Replace per-candidate Sequence copies with chain nodes in
BeamSearch (was: NameFinderME memory allocation prevents scaling)
> Replace per-candidate Sequence copies with chain nodes in BeamSearch
> --------------------------------------------------------------------
>
> Key: OPENNLP-1903
> URL: https://issues.apache.org/jira/browse/OPENNLP-1903
> Project: OpenNLP
> Issue Type: Improvement
> Components: Name Finder
> Affects Versions: 3.0.0-M5
> Reporter: Kristian Rickert
> Assignee: Kristian Rickert
> Priority: Major
> Fix For: 3.0.0-M6
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> While trying to scale the NameFinderME I ran into a bottleneck - I'm opening
> this ticket as a placeholder so I don't lose track of the work
> After around 2-3 threads, the namefinder stopped scaling and churned.
> Results were still thread-safe, but the performance never gained even though
> more compute was being thrown at it.
> I'll throw more data in here as it comes in, but I'm running a yourkit
> profiler against it to see if it can identify the specific lines that are
> causing it.
> The end result, whatever the fix may be, should result in significant
> multi-threaded performance increase. Looking at the code, I suspect there's
> a growing memory allocation issue (not a leak though) that is causing it
> If I'm right, we can consider back-porting it to 2.x as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
