Merged
Conversation
s-sajid-ali
approved these changes
Mar 25, 2026
Contributor
Author
|
That problem was caused by there being 2 types of A100 nodes. I've updated with what I think are correct numbers. I've asked Shenglong in slack to confirm that both kinds have 4 GPUs per node. I think it's the only way the math works out, but wanted to check. |
Member
|
Yup, followed the discussion on slack so that makes sense now. |
|
Contributor
Author
|
I didn't hear back about my question, so let's go ahead an merge this if it looks ok to you. The math makes sense now and I can make a new PR if/when I hear back that it's wrong. How does that sound? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The numbers for A100 seem off:
The A100 numbers for cpus and memory per node aren't coming out evenly for me. From the slide I've got 43 nodes, 3296 cpus, and 39424 memory:
cpus per node = 3296 / 43 = 76.65
memory per node = 39424 / 43 = 916.83
Seems like memory might not be an integer, but cpus per node should be, so is there a typo in the slide or am I doing something wrong? Everything else came out evenly.
Posted this in slack too.