fix(slurm): correct vNUMA socket and SMT thread calculations in util.py#5683
Conversation
Summary of ChangesHello, 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 updates the machine configuration logic for the Slurm GCP controller. It refines how sockets, threads, and cores are calculated for various instance families to better align with hardware specifications and instance template settings. Highlights
Using Gemini Code AssistThe 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
Customization To customize the 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 Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. 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
|
There was a problem hiding this comment.
Code Review
This pull request expands the sockets property in util.py to include logic for n2d, n2, and n1 machine families and updates the c3 and c4 socket counts. It also corrects the cores_per_socket calculation in template_machine_conf. Feedback suggests refactoring the complex nested ternary logic for c3 and c4 to improve maintainability and renaming the threadsPerCore variable to threads_per_core to adhere to PEP 8 naming conventions.
f487887
into
GoogleCloudPlatform:develop
This PR is a solution to the issue - #5668
This pull request updates the machine configuration logic for the Slurm GCP controller. It refines how sockets, threads, and cores are calculated for various instance families to better align with hardware specifications and instance template settings.
Changes:
Tested locally to verify this change fixes the issue: