Loading video...

Video Failed to Load

Go Home

Today on DF: is the RTX 2080 Ti the ultimate "fine wine" GPU? It's a win for balanced hardware, features and memory. Here's how it stacks up against RTX 5060 and others seven years after its launch:

28,300 views • 1 year ago •via X (Twitter)

7 Comments

Milton's profile picture
Milton1 year ago

Joke is on everybody else - I'm still using a 980 Ti

RedDeer.Games's profile picture
RedDeer.Games1 year ago

We can't spill the beans about the release date of Maki: Paw of Fury, but make no mistake, things are happening! 🫘😎 We remind you that the game is coming to #NintendoSwitch and #PC #Steam and you can play the demo on PC, here ⤵️ >>> Have a great day!

Krytopsy's profile picture
Krytopsy1 year ago

To add more context, the RTX 2080 Ti was launched almost 7 years ago.

VamosReal 🇵🇸's profile picture
VamosReal 🇵🇸1 year ago

Base PS5 outperforms the 3080 Ti / 4070 Super, PC builds!

Wokest's profile picture
Wokest1 year ago

Isn't this exactly the kind of content that Rich said he would never do?

Dochex's profile picture
Dochex1 year ago

Are you going to say people should own an RTX card again in this one? Think of the developers, they can place lights faster! 🤣

m1k33's profile picture
m1k331 year ago

Seeing Jensen out of his leather jacket is crazy

Related Videos

#Battlefield6 NVIDIA DLSS 4 Reveal Trailer 📽️ The game includes support for DLSS 4 with Multi Frame Generation, DLSS Frame Generation, DLSS Super Resolution, DLAA, and NVIDIA Reflex. Desktop GPUs Performance At 4K, Ultra settings, DLSS 4 with Multi Frame Generation and DLSS Super Resolution multiply Battlefield 6's GeForce RTX 50 Series frame rates by an average of 3.8X. ▪️ GeForce RTX 5090 performance rockets to over 470 FPS. ▪️ GeForce RTX 5080 exceeds 330 FPS. ▪️ GeForce RTX 5070 Ti is in touching distance of 300 FPS. ▪️ GeForce RTX 5070 surpasses 230 FPS. At 2560x1440, Ultra settings, DLSS 4 with Multi Frame Generation and DLSS Super Resolution increase Battlefield 6 frame rates by an average of 3X. ▪️ GeForce RTX 5090 runs at almost 600 FPS. ▪️ GeForce RTX 5060 Ti over 240 FPS. At 1920x1080, Ultra settings, the combination of DLSS 4 with Multi Frame Generation and DLSS Super Resolution boost Battlefield 6’s GeForce RTX 50 Series frame rates by an average of 2.9X. ▪️ Allowing every GPU in NVIDIA's line-up to play at over 230 FPS, maxing out at over 740 FPS on the GeForce RTX 5090. Laptop GPUs Performance GeForce RTX 50 Series Laptop GPUs benefit similarly from DLSS 4 with Multi Frame Generation and DLSS Super Resolution, with Battlefield 6 frame rates multiplied by 3X on average at 2560x1600, with Ultra settings, enabling performance of up to 360 FPS. At 1920x1080, Ultra settings, GeForce RTX 50 Series Laptop GPU performance increases by 2.8X on average, enabling Battlefield 6 frame rates to surpass 480 FPS, and the range to run at over 200 frames per second.

Battlefield Bulletin

30,559 views • 9 months ago

six months ago this wasn't happening on 8gb vram. running unsloth's Q4_K_XL quant of gemma 4 26b-a4b-it-qat, a sparse MoE model with only 4b active params on a single rtx 4060 laptop gpu, 8gb vram, 20+ tok/s decode. no cloud, no api, no offload hacks. just a gaming laptop on battery. what makes it fit: google's QAT (quantization aware training), plus MTP (multi token prediction) support in the latest llama.cpp builds. that combo is the single biggest unlock for local inference on low vram. rtx 3060, rtx 3070, gtx 1070, gtx 1080, rtx 4050, rtx 4060, rtx 5050, rtx 5060 — any 6-8gb consumer gpu, old or new — this model runs on it. world cup season, so i told it to build a soccer themed flappy bird clone. one shot, zero iteration, fully playable. six months ago an 8gb model could barely clone vanilla flappy bird. now it's shipping a themed game from a sparse MoE model running locally on a laptop battery. inference benchmarks: - decode throughput: 30 tok/s - context: 64k. this is the real unlock. 64k ctx is what makes a hermes agent loop viable locally on this model, not just single-turn chat. llama.cpp flags: -m gemma-4-26B-A4B-it-qat-UD-Q4_K_XL.gguf -c 64000 -cmoe --port 8080 game's deployed on my own site, built and shipped end to end with open source llm, zero closed source api dependency in the pipeline. link in the description. gguf weights on huggingface, link in the comments. pull it down, run it on whatever 8gb card is sitting in your rig. try the game and tell me your score and what you want in v2. local llms on consumer gpus stopped being a meme.

Alok

60,725 views • 24 days ago

a new 8GB VRAM GPU dense Local LLM leader was born yesterday runs on: RTX 4060 / RTX 3070 / RTX 2080. any 8GB card Qwen 3.5 9B (dense) was the go to for 6-8GB VRAM builds. Gemma 4 12B QAT (dense) just changed that. same llama.cpp + cuda 13.2. i7 12700H. 16GB RAM. same -ngl 99 flags. same 48k context. unsloth gemma-4-12b-it-Q4_K_M.gguf → 15 tok/sec @ 48k ctx unsloth gemma-4-12B-it-qat-UD-Q4_K_XL.gguf → 32 tok/sec @ 48k ctx → 26 tok/sec @ 64k ctx 64k context is a big deal. Hermes 3 agent requires 64k minimum to run. you're now getting full hermes compatible context on a budget consumer GPU at 26 tok/sec locally. 2.1x faster on identical hardware. and here's the part that breaks your brain: the QAT-UD-Q4_K_XL is actually SMALLER than the Q4_K_M "XL" why? QAT = Quantization Aware Training Google didn't train the model first and compress it later they trained it to be quantized from day one the weights already know how to survive low precision that's why you get more quality per byte llamacpp flags: -m gemma-4-12B-it-qat-UD-Q4_K_XL.gguf -cnv -ngl 99 -c 48000 -v fits in 8GB VRAM clean. no API. no cloud. no subscription. and this isn't even the MTP variant yet Gemma-4-E2B QAT runs on 3GB RAM, E4B on 5GB, 12B on 7GB, 26-A4B on 15GB and 31B on 18GB. I have benchmarked the 26b and 31b qat as well on a single RTX 4090, checkout the comments for details. If you have a 6GB or 8GB VRAM GPU, post your numbers. more benchmarks and configs coming soon

Alok

259,993 views • 1 month ago