Skip to content

Update recommended FI_UNIVERSE_SIZE setting for startup script - #4782

Merged
samskillman merged 1 commit into
GoogleCloudPlatform:developfrom
linsword13:ofi-tuning
Nov 24, 2025
Merged

samskillman merged 1 commit into
GoogleCloudPlatform:developfrom
linsword13:ofi-tuning

Conversation

@linsword13

Copy link
Copy Markdown
Member

This change makes libfabric to behave consistently, regardless whether it is dynamic or static built.

Submission Checklist

NOTE: Community submissions can take up to 2 weeks to be reviewed.

Please take the following actions before submitting this pull request.

  • Fork your PR branch from the Toolkit "develop" branch (not main)
  • Test all changes with pre-commit in a local branch #
  • Confirm that "make tests" passes all tests
  • Add or modify unit tests to cover code changes
  • Ensure that unit test coverage remains above 80%
  • Update all applicable documentation
  • Follow Cluster Toolkit Contribution guidelines #

@linsword13
linsword13 requested review from a team and samskillman as code owners October 23, 2025 22:01
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @linsword13, 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 addresses an inconsistency in libfabric's behavior by modifying a critical environment variable within the startup script. The change specifically targets the FI_UNIVERSE_SIZE setting, which is crucial for how libfabric operates, ensuring a uniform experience across different build configurations.

Highlights

  • FI_UNIVERSE_SIZE Update: The FI_UNIVERSE_SIZE environment variable in the startup-script/main.tf module has been updated from 3072 to 1024. This adjustment aims to ensure consistent behavior for libfabric regardless of whether it is dynamically or statically built.
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 or @gemini-code-assist . 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.

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. ↩

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

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.

Code Review

This pull request updates the FI_UNIVERSE_SIZE environment variable from 3072 to 1024 within the startup script. According to the description, this is to ensure consistent behavior for libfabric regardless of whether it's built statically or dynamically. The change is straightforward and seems correct. I have added one suggestion to include a comment explaining the reason for this specific value to improve code maintainability.

Comment thread modules/scripts/startup-script/main.tf
@linsword13

Copy link
Copy Markdown
Member Author

@samskillman, any concern regarding this change? (I tried to apply label to the PR, but didn't have the permission.)

@bytetwin

bytetwin commented Nov 6, 2025

Copy link
Copy Markdown
Collaborator

I don't see any issues with this change as its restricted only rdma networking through this flag https://github.com/search?q=repo%3AGoogleCloudPlatform%2Fcluster-toolkit%20set_ofi_cloud_rdma_tunables&type=code

@bytetwin

bytetwin commented Nov 6, 2025

Copy link
Copy Markdown
Collaborator

/gcbrun

@bytetwin bytetwin added the release-improvements Added to release notes under the "Improvements" heading. label Nov 6, 2025
@linsword13

Copy link
Copy Markdown
Member Author

Thanks @bytetwin for the review. Looks like the PR is waiting for another approver. @samskillman would you be able to take a look? Thanks!

@linsword13

Copy link
Copy Markdown
Member Author

Thanks @bytetwin for the review. Looks like the PR is waiting for another approver. @samskillman would you be able to take a look? Thanks!

@bytetwin @samskillman, gentle ping. Thanks!

This change makes libfabric to behave consistently, regardless whether it is dynamic or static built.
@samskillman
samskillman merged commit af4934f into GoogleCloudPlatform:develop Nov 24, 2025
11 of 66 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-improvements Added to release notes under the "Improvements" heading.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants