- Oct 26, 2008
- 2,112 (0.53/day)
|System Name||Budget AMD System|
|Processor||Threadripper 1900X @ 4.025Ghz (100x40.25 @ 1.325V)|
|Motherboard||Gigabyte X399 Aorus Gaming 7|
|Cooling||EKWB X399 Monoblock|
|Memory||4x8GB GSkill TridentZ RGB 14-14-14-34 CR1 @ 2933|
|Video Card(s)||XFX Radeon RX Vega₆⁴ Liquid @ 1,800Mhz Core, 1100 HBM2|
|Storage||1x ADATA SX8200 NVMe, 1x Segate 2.5" FireCuda 2TB SATA, 1x 500GB HGST SATA|
|Display(s)||Vizio 22" 1080p 60hz TV (Samsung Panel)|
|Power Supply||Seasonic X Series 850W KM3|
|Software||Windows 10 Pro x64|
The way HBCC works, is, its its own memory management system. The game tells it what it needs and it decides what gets loaded to VRAM or System RAM. I've read the white paper on it. I'll see if I can find it seeing as AMD's website's link to it is broken.This is not what HBCC does. HBCC moves data between RAM and VRAM. There is no other way to do that beyond PCIe. HBCC extends "VRAM" and has its own paging system to keep the most used pages in VRAM and moving in the other parts as needed from RAM. Whether this is a benefit effectively depends on how well game's own internal data paging/streaming system works.
Grr.. Used to have it... can't find it... Google here I come.
Yea, it can do all that. Neither of us are wrong. So not debating that. lol. I probably could have explained it better though. :-(