Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

jrmccluskey
Copy link
Contributor

Adds a class to abstract away the signaling of throttling to the SDK worker (for now this more clearly codifies the existing metric-based mechanism, but this also allows us to replace that mechanism in the future.) Also adds a new AdaptiveThrottler subclass that handles the throttling signaling itself, which streamlines code using it like the RemoteModelHandler, which now uses the new class.


Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests
Go tests

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @jrmccluskey, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the handling of throttling signaling within Apache Beam's Python SDK. It introduces a new ThrottlingSignaler class to abstract the mechanism for communicating throttling events to the SDK worker and a ReactiveThrottler class that wraps the existing AdaptiveThrottler to streamline logging and signaling. The RemoteModelHandler is updated to leverage this new ReactiveThrottler, simplifying its internal throttling logic.

Highlights

  • Abstracted Throttling Signaling: A new ThrottlingSignaler class is introduced to provide a more abstract way to signal throttling duration to the SDK worker, using a cumulative metric. This design allows for future changes to the signaling mechanism without impacting callers.
  • Encapsulated Reactive Throttling: A ReactiveThrottler class, inheriting from AdaptiveThrottler, is added. This new class centralizes the logic for logging throttling events and signaling them via the ThrottlingSignaler, making the throttling implementation more self-contained.
  • Simplified RemoteModelHandler Throttling: The RemoteModelHandler's run_inference method is simplified by delegating the entire throttling loop, including logging and metric updates, to the new ReactiveThrottler's throttle() method. This reduces boilerplate and improves readability in RemoteModelHandler.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@jrmccluskey
Copy link
Contributor Author

jrmccluskey commented Aug 27, 2025

@gemini-code-assist review

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a good abstraction for handling throttling signaling by adding ThrottlingSignaler and ReactiveThrottler classes. This simplifies the RemoteModelHandler and improves code organization and maintainability. The changes are well-structured. I've left a couple of minor suggestions for improvement regarding naming and a typo.

Copy link

codecov bot commented Aug 27, 2025

Codecov Report

❌ Patch coverage is 82.60870% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 54.83%. Comparing base (f3d10e3) to head (669ab51).
⚠️ Report is 35 commits behind head on master.

Files with missing lines Patch % Lines
...on/apache_beam/io/components/adaptive_throttler.py 80.00% 4 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##             master   #35984      +/-   ##
============================================
+ Coverage     54.75%   54.83%   +0.07%     
  Complexity     1646     1646              
============================================
  Files          1060     1061       +1     
  Lines        163560   163946     +386     
  Branches       1189     1189              
============================================
+ Hits          89562    89901     +339     
- Misses        71845    71892      +47     
  Partials       2153     2153              
Flag Coverage Δ
python 80.84% <82.60%> (+0.03%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

@jrmccluskey
Copy link
Contributor Author

test breakage on the ML tests is unrelated, workflow is red on master

@jrmccluskey
Copy link
Contributor Author

assign set of reviewers

Copy link
Contributor

Assigning reviewers:

R: @claudevdm for label python.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

@jrmccluskey
Copy link
Contributor Author

CC: @damccorm

Copy link
Contributor

@damccorm damccorm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, this is very clean! It would be great to follow up with a small pr with an example in https://github.com/apache/beam/tree/master/sdks/python/apache_beam/examples that we can merge once the release is out. Also maybe a small update to https://beam.apache.org/documentation/io/developing-io-python/ to mention handling throttling.

While its a simple code feature, I think exposing this so cleanly will help a lot of users.


class ReactiveThrottler(AdaptiveThrottler):
""" A wrapper around the AdaptiveThrottler that also handles logging and
signaling throttling to the SDK harness.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we include example usage here and be a little more descriptive on what this does?

I think we want people to use this instead of AdaptiveThrottler, so it would be better to be explicit about the UX

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, could we update CHANGES.md?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated CHANGE.md + added a pseudocode workflow for users in the docstring

@jrmccluskey jrmccluskey merged commit 35969b3 into apache:master Sep 2, 2025
120 of 124 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants