fix(sfcompute): report H100 memory as 80 GiB - #140
Merged
drewmalin merged 2 commits intoJul 31, 2026
Conversation
masonsfc
marked this pull request as ready for review
July 31, 2026 20:13
drewmalin
approved these changes
Jul 31, 2026
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
3 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.
Summary
Why
SF Compute stored the advertised 80 GB value as decimal gigabytes and then converted it to an integer GiB value. That conversion truncated 74.5 GiB to 74, so Brev displayed less GPU memory for SF Compute H100s than for equivalent H100 offerings from other providers.
Using GiB at the metadata boundary keeps
GPU.MemoryandGPU.MemoryBytesconsistent and reports the expected value of 80.