Skip to content

Optimze away WindmillWatermarkHold::clear when the cached hold is empty#38297

Open
arunpandianp wants to merge 1 commit intoapache:masterfrom
arunpandianp:improveWatermarkHold
Open

Optimze away WindmillWatermarkHold::clear when the cached hold is empty#38297
arunpandianp wants to merge 1 commit intoapache:masterfrom
arunpandianp:improveWatermarkHold

Conversation

@arunpandianp
Copy link
Copy Markdown
Contributor

No description provided.

@arunpandianp
Copy link
Copy Markdown
Contributor Author

R: @scwhittle

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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 introduces a performance optimization for the WindmillWatermarkHold class by preventing redundant operations when the watermark hold is already cleared. By adding an early return check, the system avoids unnecessary processing and state modifications, improving efficiency in scenarios where clear() is called on an empty state.

Highlights

  • Performance Optimization: Added a conditional check in WindmillWatermarkHold::clear to return early if the cached hold is already empty, avoiding unnecessary state updates.
  • Testing: Added a new test case testWatermarkClearNoOp to verify that clearing an empty watermark hold does not result in unnecessary state persistence.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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.

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.

@github-actions
Copy link
Copy Markdown
Contributor

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

@arunpandianp
Copy link
Copy Markdown
Contributor Author

StreamingDataflowWorkerTest tests fail due to problems with mocks, looking into fixing them.


@Override
public void clear() {
if (cachedValue != null && !cachedValue.isPresent() && localAdditions == null) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

How about:

localAdditions = null;
if (cachedValue == null || cachedValue.isPresent()) {
  cleared = true;
  cachedValue = Optional.absent();
}

no reason to not skip sending backend clear if there were localadditions

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