Citrini analyst Jukan stated that NVIDIA is discussing adjustments to the HBM configuration of the Rubin Ultra GPU, planning to change the main version from HBM4E 12Hi 384GB to HBM4 8Hi 192GB, followed by a subsequent release of an HBM4E 8Hi variant. If NVIDIA’s CoWoS capacity allocation reaches 1.2 million units in 2027, accelerator production is expected to reach approximately 9.9 million units, with around 1.6 million units of Rubin Ultra. With the lower-spec HBM configuration, NVIDIA’s HBM demand in 2027 is projected to decline from 241 billion Gb to 216 billion Gb, a reduction of about 10%, resulting in an overall HBM demand decrease of approximately 4%. By adjusting its HBM configuration, NVIDIA aims to increase accelerator production amid limited HBM supply.
NVIDIA Considers Adjusting HBM Configuration for the Rubin Ultra GPU
AiCoinShare
NVIDIA is reportedly adjusting the HBM configuration for the Rubin Ultra GPU, shifting the main version from HBM4E 12Hi 384GB to HBM4 8Hi 192GB, with a later HBM4E 8Hi variant. If CoWoS production reaches 1.2 million units in 2027, accelerator output could hit 9.9 million, including 1.6 million Rubin Ultra units. The lower HBM specification may reduce HBM demand by 10% to 216 billion Gb, a 4% overall decline. The change aims to increase output amid tight HBM supply. This update brings the latest crypto news on NVIDIA’s hardware strategy.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.