BreakIterator.GetBoundaries is exponentially slow depending on the size of the source text #127
Labels
Comments
atlastodor
added a commit
to atlastodor/icu-dotnet
that referenced
this issue
Mar 31, 2020
…w depending on the size of the source text
ermshiperete
pushed a commit
that referenced
this issue
Apr 1, 2020
…ing on the size of the source text
|
Fixed by #128 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
BreakIterator.GetBoundaries is exponentially slow depending on the size of the source text. In other words, the larger the size of the text parameter string is, the slower the function is, and the curve is not linear.
To Reproduce
string content = "... some large text, about 100KB ... ";
BreakIterator.GetBoundaries(BreakIterator.UBreakIteratorType.WORD, new Locale("eng"), content, false); // Takes about 10 secs.
Expected behavior
The BreakIterator.GetBoundaries to finish within milliseconds.
Environment
The text was updated successfully, but these errors were encountered: