In this article
A800 80 GB server configurations need their own inventory and support record. They must not be confused with the A800 40 GB Active workstation board.
Separate the server product from the active board
The archived Lenovo product guide identifies A800 server configurations with 80 GB of local memory in PCIe and SXM4 form factors. These are different products from the A800 40 GB Active card. The OEM guide marks its product withdrawn, which is relevant to an existing installation but does not establish current stock elsewhere. This table deliberately uses the conservative HBM family description where the exact generation should be checked against the installed part number and its matching specification.
| Variant | Local memory, GB | Memory type | Published board power, W |
|---|---|---|---|
| A800 PCIe 80 GB | 80 | HBM | 300 |
| A800 SXM4 80 GB | 80 | HBM | Not verified |
The product or OEM specification establishes the configuration: manufacturer source.
Verify the Ampere inference stack
Ampere architecture is a useful starting point for CUDA inference, not a complete serving certificate. Record the driver, CUDA runtime, engine build, selected quantization and model revision. Start with a correctness case that exercises the intended attention path, then increase request length and concurrency. An engine may select different kernels for a different numerical format. If MIG is enabled, use the visible partition capacity and profile instead of the full 80 GB figure when estimating available runtime memory.
The software boundary is documented in the inference compatibility reference.
Do not infer interconnect equivalence
Matching local memory does not make A800 interchangeable with every A100 configuration. The documented interconnect and host platform must remain part of the comparison. A multi-device model needs an explicit partitioning strategy; installation of a bridge or several modules does not automatically create one allocation spanning them. Inspect peer connectivity and collective operations in the actual server. Compare full request latency under the intended workload, since a useful single-device result can change when communication becomes a substantial part of execution.
Treat server rendering as an independent qualification
A compute accelerator may be considered by a CUDA-capable renderer, but product positioning is not proof of graphics feature coverage. Check the current engine, driver and operating-system matrix, then render a representative scene without relying on a desktop display session. Validate textures, materials, output and memory residency. Dedicated RTX hardware features should not be assumed from the A800 name. A successful render evaluation applies to that configuration and scene class, not automatically to every commercial rendering engine or plugin.
Renderer requirements are separate in the Cycles GPU manual.
Evaluate an installed system, not a catalogue promise
For an existing A800 machine, retain the exact OEM model, accelerator part numbers, cooling layout and firmware versions. Distinguish device power settings from whole-server wall consumption. Run a sustained workload and a controlled service restart, preserving logs for allocator failures and thermal behaviour. An archived product guide is a specification reference, not a supplier availability statement. Retrivium’s informational catalogue does not imply ownership of this hardware or a completed marketplace integration for the configuration described here.
Related reading: RAM and VRAM and a reproducible inference benchmark. GPU catalogue records the scope, model variants and unresolved specifications.