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

Added note on grobid concurrency configuration to README. #52

Merged

Conversation

elshimone
Copy link
Contributor

Fixes #50

@davidmezzetti davidmezzetti added this to the v2.3.0 milestone Dec 3, 2023
@davidmezzetti
Copy link
Member

Sorry to nitpick here but could we make this a bit more concise? In my experience if we have a lot of these type of edge case messages over time, it gets hard to read.

Maybe something like this:

Note: Depending on the number of CPUs in your system, the GROBID engine pool may be exhausted when parsing PDFs, resulting in a 503 error. This can be fixed by increasing the concurrency and/or poolMaxWait setting in the GROBID configuration file.

If you're strapped for time, I can handle myself. You've already done a bunch to help and it's been greatly appreciated.

@davidmezzetti davidmezzetti merged commit 88119cc into neuml:master Dec 3, 2023
3 checks passed
@davidmezzetti
Copy link
Member

Never mind, I made the minor edit. Thank you for the additions to paperetl and paperai!

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

Successfully merging this pull request may close these issues.

Scaling to create a proccess per cpu core overwhelms grobid service
2 participants