• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

NVIDIA GeForce RTX 2060 to Ship in Six Variants Based on Memory Size and Type

Joined
Feb 18, 2005
Messages
1,875 (0.37/day)
Likes
1,149
Location
South Africa
System Name Firelance
Processor i7-3770K @ 4.6GHz / 1.23V
Motherboard Gigabyte Z77X-UD5H @ F16h mod BIOS
Cooling Corsair H105 + 4x Gentle Typhoon 1850
Memory 2x 8GB Crucial Ballistix Sport DDR3-1600 CL9 @ CL7
Video Card(s) MSI GTX 1070 Armor OC with Gaming X BIOS @ 2000 core / 2300 mem
Storage 2x 256GB 840 Pro (RAID-0) + 3TB Deskstar 7K3000 + 512GB BX300 + 8TB WD Purple
Display(s) Dell U2713HM (25x14) + Acer P243W (19x12)
Case Thermaltake Core X31
Audio Device(s) Corsair VOID Wireless
Power Supply Seasonic SS-760XP² Platinum
Mouse Logitech G400
Keyboard Logitech G19
Software Windows 7 Professional x64 Service Pack 1

FordGT90Concept

"I go fast!1!11!1!"
Joined
Oct 13, 2008
Messages
24,070 (6.37/day)
Likes
13,216
Location
IA, USA
System Name BY-2015
Processor Intel Core i7-6700K (4 x 4.00 GHz) w/ HT and Turbo on
Motherboard MSI Z170A GAMING M7
Cooling Scythe Kotetsu
Memory 2 x Kingston HyperX DDR4-2133 8 GiB
Video Card(s) Sapphire NITRO+ RX 590 Special Edition 8 GiB DVI + HDMI
Storage Crucial MX300 275 GB, Seagate Exos 12 TB 7200 RPM
Display(s) Samsung SyncMaster T240 24" LCD (1920x1200 HDMI) + Samsung SyncMaster 906BW 19" LCD (1440x900 DVI)
Case Coolermaster HAF 932 w/ USB 3.0 5.25" bay
Audio Device(s) Realtek Onboard, Micca OriGen+
Power Supply Enermax Platimax 850w
Mouse SteelSeries Sensei RAW
Keyboard Tesoro Excalibur
Software Windows 10 Pro 64-bit
Benchmark Scores Faster than the tortoise; slower than the hare.
I talked to someone in the know about the theoretical of a 32-bit D3D10 game and how that relates to VRAM. Textures practically have to pass through the RAM to reach the VRAM. The only way to not do that is via DMA which is very fringe stuff.

My understanding is that there's a variety of ways to make it crash because that RAM limitation is absolute.
1) If you try to load too many resources, GART will overflow crashing the executable.
2) If you try to load a huge asset (depending on conditions but could be smaller than 3 GiB in size) , it will crash because the RAM can't hold the asset before handing it to the VRAM.
3) If you try to hold too many assets in RAM in transit to VRAM and you fail to release them the RAM fast enough and it goes over the virtual memory limit, it will crash.

In other words, even under 32-bit D3D10, you're dancing on a razer's edge when dealing with VRAM. VRAM (unless DMA is used which good luck with that) is practically limited by addressable RAM space.

Coming full circle, this is fundamentally why Fury X 4 GiB and GTX 970 3.5 GiB were okay a few years ago but not so much now. Any game that might need 64-bit address space is usually 64-bit. The days of claustrophobic memory usage are gone.
 
Joined
May 22, 2015
Messages
5,203 (3.81/day)
Likes
2,224
Processor Intel i5-6600k
Motherboard ASRock Z170 Extreme7+
Cooling Arctic Cooling Freezer i11
Memory 2x8GB DDR4 2400 G.Skill
Video Card(s) EVGA GTX 1060 SC
Storage 128 and 256GB OCZ Vertex4, 500GB Samsung 850 EVO, 1TB Crucial MX300 and 3TB Seagate
Display(s) HP ZR24w
Case Chieftec BX01
Power Supply Seasonic 620W M12
Mouse Logitech G502 Proteus Core
Keyboard G.Skill KM780R
I talked to someone in the know about the theoretical of a 32-bit D3D10 game and how that relates to VRAM. Textures practically have to pass through the RAM to reach the VRAM. The only way to not do that is via DMA which is very fringe stuff.

My understanding is that there's a variety of ways to make it crash because that RAM limitation is absolute.
1) If you try to load too many resources, GART will overflow crashing the executable.
2) If you try to load a huge asset (depending on conditions but could be smaller than 3 GiB in size) , it will crash because the RAM can't hold the asset before handing it to the VRAM.
3) If you try to hold too many assets in RAM in transit to VRAM and you fail to release them the RAM fast enough and it goes over the virtual memory limit, it will crash.

In other words, even under 32-bit D3D10, you're dancing on a razer's edge when dealing with VRAM. VRAM (unless DMA is used which good luck with that) is practically limited by addressable RAM space.

Coming full circle, this is fundamentally why Fury X 4 GiB and GTX 970 3.5 GiB were okay a few years ago but not so much now. Any game that might need 64-bit address space is usually 64-bit. The days of claustrophobic memory usage are gone.
DMA access used to be everywhere a while back, not sure whether Win10 restricts is somehow (and I wouldn't be surprised if it does).
As for loading huge textures, two things. First, there's this thing called streaming - you don't have to keep the entire thing into RAM at the same time to load it. Second, I'm pretty sure no game uses a 3GB piece of texture.
 

FordGT90Concept

"I go fast!1!11!1!"
Joined
Oct 13, 2008
Messages
24,070 (6.37/day)
Likes
13,216
Location
IA, USA
System Name BY-2015
Processor Intel Core i7-6700K (4 x 4.00 GHz) w/ HT and Turbo on
Motherboard MSI Z170A GAMING M7
Cooling Scythe Kotetsu
Memory 2 x Kingston HyperX DDR4-2133 8 GiB
Video Card(s) Sapphire NITRO+ RX 590 Special Edition 8 GiB DVI + HDMI
Storage Crucial MX300 275 GB, Seagate Exos 12 TB 7200 RPM
Display(s) Samsung SyncMaster T240 24" LCD (1920x1200 HDMI) + Samsung SyncMaster 906BW 19" LCD (1440x900 DVI)
Case Coolermaster HAF 932 w/ USB 3.0 5.25" bay
Audio Device(s) Realtek Onboard, Micca OriGen+
Power Supply Enermax Platimax 850w
Mouse SteelSeries Sensei RAW
Keyboard Tesoro Excalibur
Software Windows 10 Pro 64-bit
Benchmark Scores Faster than the tortoise; slower than the hare.
Developers use the methods provided to them by APIs like D3D, OpenGL, and Vulkan which don't use DMA to move the textures. DMA hasn't been used in earnest since before those APIs became common. All of those APIs also support super textures either for sectioning (using segments of a larger image to reduce HDD/SDD load) or sky domes.

Yes, streaming, but most engines that are big on streaming (like UE4) and are of the era where >4 GiB VRAM can be used are also already 64-bit so it's a non-issue. This is where you run into problems with graphics cards that have <4 GiB VRAM because the API is having to shuffle assets between RAM and VRAM which translates to stutter.
 
Joined
May 22, 2015
Messages
5,203 (3.81/day)
Likes
2,224
Processor Intel i5-6600k
Motherboard ASRock Z170 Extreme7+
Cooling Arctic Cooling Freezer i11
Memory 2x8GB DDR4 2400 G.Skill
Video Card(s) EVGA GTX 1060 SC
Storage 128 and 256GB OCZ Vertex4, 500GB Samsung 850 EVO, 1TB Crucial MX300 and 3TB Seagate
Display(s) HP ZR24w
Case Chieftec BX01
Power Supply Seasonic 620W M12
Mouse Logitech G502 Proteus Core
Keyboard G.Skill KM780R
Developers use the methods provided to them by APIs like D3D, OpenGL, and Vulkan which don't use DMA to move the textures. DMA hasn't been used in earnest since before those APIs became common. All of those APIs also support super textures either for sectioning (using segments of a larger image to reduce HDD/SDD load) or sky domes.
That doesn't prevent said APIs from doing DMA internally.

Yes, streaming, but most engines that are big on streaming (like UE4) and are of the era where >4 GiB VRAM can be used are also already 64-bit so it's a non-issue. This is where you run into problems with graphics cards that have <4 GiB VRAM because the API is having to shuffle assets between RAM and VRAM which translates to stutter.
Streaming is the non-naive way to handle large assets in programming.
 

FordGT90Concept

"I go fast!1!11!1!"
Joined
Oct 13, 2008
Messages
24,070 (6.37/day)
Likes
13,216
Location
IA, USA
System Name BY-2015
Processor Intel Core i7-6700K (4 x 4.00 GHz) w/ HT and Turbo on
Motherboard MSI Z170A GAMING M7
Cooling Scythe Kotetsu
Memory 2 x Kingston HyperX DDR4-2133 8 GiB
Video Card(s) Sapphire NITRO+ RX 590 Special Edition 8 GiB DVI + HDMI
Storage Crucial MX300 275 GB, Seagate Exos 12 TB 7200 RPM
Display(s) Samsung SyncMaster T240 24" LCD (1920x1200 HDMI) + Samsung SyncMaster 906BW 19" LCD (1440x900 DVI)
Case Coolermaster HAF 932 w/ USB 3.0 5.25" bay
Audio Device(s) Realtek Onboard, Micca OriGen+
Power Supply Enermax Platimax 850w
Mouse SteelSeries Sensei RAW
Keyboard Tesoro Excalibur
Software Windows 10 Pro 64-bit
Benchmark Scores Faster than the tortoise; slower than the hare.
That doesn't prevent said APIs from doing DMA internally.
But they don't and that's the point. Everything in VRAM flows through RAM.

The argument I made before about 32-bit and VRAM being intrinsically linked is effectively true. Now that the 32-bit barrier is gone, VRAM usage has soared in games that can use it.
 
Last edited:
Top