Skip to content

GCS artifact storage should be async #1346

Closed
Closed

Description

@condorcet

At this moment GCS artifact storage implementation relies on GCS client which does not support asyncio.

This results in the event loop being blocked on every I/O operation, which is critical for production use.

I believe this can be solved in a more generic way with S3 compatible interface (e.g. #555).
But as a first iteration, we can simply run the current methods with a thread pool executor to satisfy the minimal async behavior.

Activity

  1. added
    services[Component] This issue is related to runtime services, e.g. sessions, memory, artifacts, etc
    on Jun 14, 2025
  2. added theissue type on Jul 2, 2025
  3. hangfei commented on Jul 2, 2025

    @hangfei
    Collaborator

    @DeanChensj is this already fixed?

  4. changed the issue type fromtoon Jul 7, 2025
  5. added
    wip[Status] This issue is being worked on. Either there is a pending PR or is planned to be fixed
    on Jul 16, 2025
  6. removed
    wip[Status] This issue is being worked on. Either there is a pending PR or is planned to be fixed
    on Jul 22, 2025
  7. DeanChensj commented on Jul 22, 2025

    @DeanChensj
    Collaborator

    Resolved by #1347

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

Metadata

Metadata

Assignees

Labels

services[Component] This issue is related to runtime services, e.g. sessions, memory, artifacts, etc

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions