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

Response performance after upload via API #767

Open
alexanderadam opened this issue Aug 22, 2024 · 1 comment
Open

Response performance after upload via API #767

alexanderadam opened this issue Aug 22, 2024 · 1 comment
Labels

Comments

@alexanderadam
Copy link
Contributor

alexanderadam commented Aug 22, 2024

We're currently struggling with high resource usage when processing a lot of documents.
Right now it's not possible to disable OCR processing even if we know that we don't need OCR in these cases or even the different document formats.

@alexanderadam alexanderadam changed the title Faster response performance after upload via API Response performance after upload via API Aug 28, 2024
jendib pushed a commit that referenced this issue Sep 7, 2024
@jendib
Copy link
Member

jendib commented Sep 7, 2024

As you know the OCR is done by Tesseract which is done by another team/project so we cannot do much about the resource usage. From my experience a fast CPU is indeed required.

@jendib jendib added the question label Sep 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants