Skip to content

[Feature] Support async jobs and later retrieval #320

@syntaxsdev

Description

@syntaxsdev

The current ASR framework is cool, however there becomes a bigger issue when any audio larger than a seconds in loaded. When upload files in excess of 50MB, the service starts to fail, where requests commonly exceed 30 seconds and can prompt gateway timeouts, etc when deployed on Kubernetes services.

I propose a batch processor, where a submission can be made and a ticket or id is provided so a user can retrieve the results later.

A small database can be used, such as sqlite, and then data can be automatically deleted x amount of time after it's first retrieval.

Something along the lines of:

POST /submit_job -> uploads and queues/batches
GET /retrieve -> returns the results if ready other a not ready code

This would harden the application and make it more robust.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions