Identify the right H100 variant
This offering corresponds to the H100 PCIe with 80 GB HBM2e, on the Hopper architecture. It refers neither to the H100 SXM with 80 GB HBM3 nor to an H100 NVL. Carry this full designation into your qualification documents so that a later comparison does not mix up different hardware versions.
The PCIe form factor describes the product, but on its own it does not give the specifications of the whole machine. For your acceptance testing, start from the visible resources and the application's requirements, without inferring a network configuration or a link between cards from the model.
Separate loading, computation and results
Break a representative run into three stages: data loading, GPU processing and output generation. Keep their durations and peak memory along with the software versions. If inputs arrive slowly or export dominates, the priority may be to organize files and work batches before changing the configuration.
Compare with an A100 without changing the protocol
The A100 SXM with 80 GB is an alternative for an application already validated on Ampere. The H100 SXM is the other Hopper variant to consider. In both cases, keep the same numerical parameters and the same data: updating the software at the same time would blur the comparison and complicate the migration decision.
Rent to decide, then to execute
A 3-day rental can be used to qualify a specific scenario. A 7-day period lets you schedule several series into the team's planning. For 30 days, prepare a prioritized queue and a checkpoint before each new data family.
Select the number of batches, each comprising one card, then the duration and the environment. Provide the contact details of the person who will follow the order. Before the full campaign, have the acceptance test result approved by the person responsible for processing.