Details

    • Sub-task
    • Status: Open
    • P3
    • Resolution: Unresolved
    • None
    • None
    • beam-model
    • None

    Description

      The current user facing API looks like a future which can be resolved later, we want to minimize the amount of time a user spends blocking after queuing up all their requests.

      Google Cloud Dataflow has experienced performance problems in the past without having support for a batch API because solutions that add fixed delays ("wait for N milliseconds for a batch to form") have caused large problems for pipelines with few numbers of keys.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              lcwik Luke Cwik
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: