Skip to content

Response performance after upload via API #767

Open
@alexanderadam

Description

@alexanderadam
Contributor

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.

Activity

changed the title [-]Faster response performance after upload via API[/-] [+]Response performance after upload via API[/+] on Aug 28, 2024
added a commit that references this issue on Sep 7, 2024
jendib

jendib commented on Sep 7, 2024

@jendib
Member

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.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @alexanderadam@jendib

        Issue actions

          Response performance after upload via API · Issue #767 · sismics/docs