Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance issues with UnicodeTokenizer #80

Open
GoogleCodeExporter opened this issue May 25, 2015 · 0 comments
Open

Performance issues with UnicodeTokenizer #80

GoogleCodeExporter opened this issue May 25, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. call ArticleExtractor.getInstance().getText() on the example data 
(Stability.html) 

What is the expected output? What do you see instead?
The extraction takes a very long time (1-3 minutes depending on hardware and 
jvm load) with heavy memory re-allocations in StringBuilder during 
Matcher.replaceAll calls. HTML of this size typically takes 2-3s on the same 
hardware.

What version of the product are you using? On what operating system?
1.1.0 & 1.2.0 on Ubuntu 12.04 with Oracle JVM
java version "1.7.0_67"
Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

Please provide any additional information below.
The attached patch fixes the regressive performance and improves the 
tokenization of tokens containing word, non-word, and transitional characters.

Note: I am not the author of the attached html file causing regressive 
performance.

Original issue reported on code.google.com by [email protected] on 14 Oct 2014 at 7:22

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant