In this article
The RTX 3090 Ti has 24 GB and reference 450 W; equal capacity with the RTX 3090 does not establish equal power or execution behavior.
Ampere Ti with a defined capacity
The RTX 3090 Ti has 24 GB GDDR6X and reference board power of 450 W. The RTX 3090 also has 24 GB, but its reference power differs. Moving a worker therefore requires more than comparing capacity. The table concerns one GPU. Nominal memory is not the remainder after driver initialization and background activity. For an existing Ti, record board manufacturer, cooling design, supply and chassis placement. This profile assigns no gain over the ordinary 3090: neither the suffix nor a specified watt difference produces a performance ratio. Use observed workload evidence for that comparison.
| Official variant | Memory per GPU | Memory type | Board power | Evidence |
|---|---|---|---|---|
| NVIDIA GeForce RTX 3090 Ti — 24 GB NVIDIA comparison design | 24 GB | GDDR6X | 450 W | Specification |
Validate the Ampere inference path
Match vLLM requirements to the actual software stack and checkpoint. Ampere clears the hardware minimum while dtype, quantization and selected kernels need separate validation. Preserve model, tokenizer, context and output limit for the RTX 3090 Ti. Measure working memory after loading on a bounded corpus. A passing sequential request does not establish admissible concurrency. Examine KV budget and active requests in another experiment. CPU or additional GPU involvement must remain visible: success does not establish that the whole task was resident on one GPU. Record placement with the software settings.
Accept a saved Cycles scene
Blender Cycles CUDA and OptiX require a suitable driver and build. Run the Ti with a project containing verified assets and quality settings. A supporting backend uses RTX hardware tracing rather than every renderer doing so automatically. Record preparation, GPU execution and resulting image. Host RAM use represents another execution condition. Do not infer fit from one small frame without the required geometry and textures. Previous task state also matters: a resident LLM may leave less available memory even though inventory identity and nominal capacity remain unchanged. Observe actual resource ownership before rendering.
Repeat work under normal settings
Server integration benefits from a sequence of matched jobs rather than only an initial short burst. A bounded test observes memory, temperature and available device state reasons at the beginning, middle and end. Keep tasks and settings constant. If results deteriorate, investigate cooling, host load and residual processes without forcing clocks or disabling protections. The 450 W figure is not the whole system budget: CPU, RAM and storage consume power too. The selected AIB card needs actual connectors and airflow rather than an assumption that any server with a sufficiently rated PSU is suitable.
Preserve workload stability evidence
The package contains LLM and scene manifests, planned repetitions, observed statuses and measurement time series. Growing residual memory suggests examining lifecycle and caches; duration changes with temperature events suggest investigating device conditions. Correlation does not establish causation. The decision describes RTX 3090 Ti repeatability in a particular chassis and stack release. It promises neither constant TPS nor every frame duration or absence of all faults. Comparing the RTX 3090 requires a separate experiment with matched files, measurement boundaries and comparable operating conditions. Keep the tested limits beside the accepted role.
Local LLMs on 24GB VRAM: Test More Than the Weights · GPU power caps: an energy and latency experiment · GPU catalog