Skip to content

pubsubsink writes messages sequentially #53

@andremissaglia

Description

@andremissaglia

pubsubsink waits for the last message to be completely delivered before sending the next one.

This is inefficient, because if we don't batch the requests, the throughput is limited to 1/write_latency .

A solution would be to .Get the result only once all messages have been published.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions