Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-11730

Reduce context switches for dataflow streaming appliance getdata reads

Details

    • Bug
    • Status: Resolved
    • P2
    • Resolution: Fixed
    • None
    • Missing
    • runner-dataflow
    • None

    Description

      Currently reads are batched and issued from a separate thread pool of reading threads. However in the case that there is not read queuing due to the max # of parallel requests, switching threads is unnecessary and adds additional context swithing overhead.

      In a benchmark I observed 5% cpu spent on LockSupport.park which some googling indicates is due to context switching.

      Attachments

        Issue Links

          Activity

            People

              scwhittle Sam Whittle
              scwhittle Sam Whittle
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 2h 10m
                  2h 10m