Verdict

Two machines with the same 24 GB of video memory, built five years apart: Sam's desktop with an RTX 3090 from 2020, and the student's MSI laptop with an RTX 5090 Laptop GPU from 2025.

🟡 For today's SDXL work: about even. Her laptop pulls ahead on FP8 / FP4 models; Sam's desktop is better at running flat out for hours.

Same ceiling: both have 24 GB of VRAM, so every model that fits on one fits on the other (SDXL, Flux, LoRA training).

Same "engine size": both have 10,496 CUDA cores, and memory bandwidth differs by only 4% (936 vs 896 GB/s).

Her advantage is newer, not bigger: 5th-generation Tensor cores with hardware FP8 and FP4, and a cache 10× larger. It reaches 3090-level speed on 175 W instead of 390 W.

Sam's advantage is power and cooling: a desktop holds full speed indefinitely. A laptop running at 175 W can slow down during long batches as it heats up.

Not benchmarked: neither machine has been timed on the same job yet. The test in the last section settles it in 10 minutes.

The two machines

Sam's desktop

Custom build · Gigabyte B550 Gaming X · Windows 10 Pro measured
  • GPU: NVIDIA GeForce RTX 3090 (desktop), 24 GB GDDR6X
  • GPU power limit: 390 W (card allows up to 480 W)
  • CPU: AMD Ryzen 7 5800X, 8 cores / 16 threads
  • RAM: 64 GB DDR4-3200 (2 × 32 GB)
  • Storage: 5 drives, about 10 TB raw (Samsung 990 Pro 1 TB, 2 TB SSD, 3 HDDs)
  • Image stack: Forge, PyTorch 2.3.1 + CUDA 12.1

Student's laptop

MSI Titan 18 HX Dragon Edition Norse Myth (A2XWJG) · Windows 11 Pro 25H2 screenshot
  • GPU: NVIDIA GeForce RTX 5090 Laptop GPU, 24 GB GDDR7
  • GPU power limit: up to 175 W MSI spec
  • CPU: Intel Core Ultra 9 285HX (24 cores) core count = Intel spec
  • RAM: 96 GB DDR5-6400
  • Storage: 5.59 TB (3.11 TB used)
  • Also has: Intel integrated graphics (128 MB), used for the display only, not for AI work
"5090" in a laptop is not a desktop 5090.The RTX 5090 Laptop GPU is built on GB203, the same chip as the desktop RTX 5080, running at laptop power. A desktop RTX 5090 (GB202, 21,760 cores, 32 GB, 575 W) would be roughly twice as fast as either of these machines.

GPU head-to-head

The figures that decide image-generation speed. Click any cell for an explanation.

SpecSam: RTX 3090 desktopStudent: RTX 5090 LaptopEdge
Architecture / yearAmpere (GA102), 2020Blackwell (GB203), 2025Student
Manufacturing processSamsung 8 nmTSMC 4N (≈ 5 nm class)Student
Video memory (VRAM)24 GB GDDR6X measured24 GB GDDR7 screenshotTie
CUDA cores10,49610,496Tie
Memory bus / bandwidth384-bit · ≈ 936 GB/s256-bit · ≈ 896 GB/sTie (Sam +4%)
L2 cache6 MB64 MBStudent
Tensor cores (AI math units)3rd generation5th generationStudent
FP8 in hardwareNoYesStudent
FP4 (NVFP4) in hardwareNoYesStudent
GPU power390 W limit measuredup to 175 W specSam (sustained)
PCIe linkGen 4 ×16 measuredGen 5 ×16 specIrrelevant for this work
Upgradeable laterYes, swap the cardNo, GPU is solderedSam

Unmarked rows are published NVIDIA specifications for each GPU model.

Per workload

Estimated relative speed, with Sam's RTX 3090 = 100. estimates from architecture and published benchmark patterns. Nothing here was timed on either machine.

Workload
Sam: RTX 3090
Student: 5090 Laptop
Call
SDXL, FP16
Diana / Bella pipelines in Forge: ControlNet, ADetailer, LoRAs
100
≈ 90–130
About even
SDXL distilled (DMD2, 4 steps)
Diana Fast: short jobs, little time to heat up
100
≈ 100–130
Even / slight student edge
Flux / newer models in FP8
The 3090 has to convert FP8 back to 16-bit to compute
100
≈ 130–200
Student
NVFP4 models
The newest compressed checkpoints
no hardware support
supported
Student only
LoRA training, multi-hour
Long full load, where cooling decides
100
≈ 80–120
Even; Sam steadier
Overnight batch (hundreds of images)
Sustained output, noise, heat
100
≈ 80–110
Sam
Huge models that overflow 24 GB
Parts are offloaded to system RAM
100
faster offload
Student (96 GB DDR5)
How to read the barsThe ranges are wide on purpose. The laptop's real speed depends on whether MSI's power mode actually holds 175 W and how hot it runs. Only a timed test on both machines turns these estimates into facts.

Rest of the system

PartSamStudentMatters for image generation?
CPURyzen 7 5800X · 8C/16T measuredCore Ultra 9 285HX · 24C screenshotBarely: the GPU does the work
System RAM64 GB DDR4-3200 measured96 GB DDR5-6400 screenshotOnly when models overflow VRAM, or for large video models
Storage≈ 10 TB across 5 drives measured5.59 TB (2.48 TB free) screenshotModel library size and load times
WindowsWindows 10 Pro (build 19045)Windows 11 Pro 25H2 (build 26200)No

Practical differences

Sam's desktop wins on
Staying power
Holds full speed for hours, can be upgraded with a new card, and is cheaper to repair. It uses about 2× the power for similar speed.
Student's laptop wins on
Newer AI features
FP8 / FP4 support, more and faster RAM, portable, about half the power. Fan noise will be loud under load.
Same on both
24 GB ceiling
Neither can load a model the other can't. The largest model size she can run is the same as Sam's.
Getting full speed from the laptopMSI Center → User Scenario → Extreme Performance, and keep it plugged in. On battery or in a quiet mode, the GPU is held well below 175 W and the comparison above no longer applies. A cooling pad helps during long batches.

⚠ Software on her laptop

Sam's exact Forge folder will not run on her GPU.Read from Sam's Forge Python today measured: torch 2.3.1+cu121, supported GPU generations sm_50 … sm_90. The RTX 5090 Laptop is sm_120 (Blackwell), which needs CUDA 12.8+ and PyTorch 2.7+. A copy of Sam's folder would fail to use her GPU or would error at startup.
  1. Install a current Forge or ComfyUI build made for CUDA 12.8 (labelled "cu128").
  2. Copy only the models, LoRAs and workflow presets across from Sam's setup, not the program folder.
  3. Update the NVIDIA driver to the latest Studio or Game Ready version.
  4. Once it runs, use FP8 versions of Flux and other new models. That's where her card is ahead.

How to settle it: a real test

Run the same job on both machines and compare seconds per image.

  1. Same checkpoint (e.g. the SDXL model Sam uses for Diana HD).
  2. Same prompt, seed 12345, 1024 × 1024, 30 steps, DPM++ 2M Karras, CFG 5, no ControlNet, no ADetailer.
  3. Generate once as a warm-up and discard it, then generate 10 images in a row.
  4. Note the "Time taken" Forge prints for the 10, and divide by 10.
  5. Repeat with batch 50 to see whether the laptop slows down once it is hot.

To capture her real GPU power and clocks, she runs this in a terminal while generating:

nvidia-smi --query-gpu=name,memory.total,power.draw,power.limit,clocks.gr,temperature.gpu --format=csv -l 2

What was measured vs not

Measured today on Sam's PC GPU model, VRAM, driver 596.36, 390 W / 480 W power limits, PCIe Gen 4 ×16 (nvidia-smi) · CPU, RAM size and speed, motherboard, drives (Windows) · Forge's PyTorch 2.3.1 / CUDA 12.1 and supported GPU list (Forge's own Python).
Not measured Nothing was run on the student's laptop: her specs come from her screenshot plus published NVIDIA / MSI / Intel specs · her real power limit and temperatures under load · any timed image-generation run on either machine. Every speed figure on this page is an estimate until the test above is done.
Click any table cell
The explanation for that row appears here.