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

why crf_test took long time #36

Open
cmathx opened this issue Feb 10, 2017 · 2 comments
Open

why crf_test took long time #36

cmathx opened this issue Feb 10, 2017 · 2 comments

Comments

@cmathx
Copy link

cmathx commented Feb 10, 2017

I use a machine with 64GB memory and it has only 12GB memory. I run a test with tagger->parse() and it costs long time about 150ms. But when I run a test in machine with enough free memory, it only costs 2-3ms.
I find that most of the time spend on feature_index_->buildFeatures(this) and buildLattice() operations.
image

@Naminwang
Copy link

My machine has enough free memory, but parse() cost long time about 200ms. Do you find how to speed up the parse() interface? @cmathx

@cmathx
Copy link
Author

cmathx commented Oct 24, 2019

You can focus on mmap function in the resp. A little case costs much time is because mmap call method.

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

No branches or pull requests

2 participants