![]() However, because it also rolled in goodness from AMD’s third-gen GCN architecture, there were some gains in tessellation throughput, as well. The more recent Fiji GPU (Radeon R9 Fury X) maintained that same four-way Shader Engine configuration. The Hawaii GPU (Radeon R9 290X) incorporated some notable improvements over Tahiti (Radeon HD 7970), one of which was a more robust front end with four geometry engines instead of two. Allocating an extra 4GB of DDR4 at 3200 MT/s nudged that result up to 26.9 FPS. ![]() With the HBCC disabled, we measured 25.7 FPS. If you have 16GB installed, you don't want to lose 4GB or 8GB to the HBCC.ĪMD suggested that Unigine Heaven might reflect some influence from enabling the HBCC memory segment, so we ran the benchmark at 4K using 8x anti-aliasing and Ultra quality. Of course, the one recommendation is to have plenty of system RAM available before using the HBCC. However, AMD has shown off content creation workloads that truly need access to additional memory. Given Vega 64's 8GB of HBM2, this option is fairly forward-looking there aren't many games that need more. Per AMD, once the HBCC is operating, it'll monitor the utilization of bits in local GPU memory and, if needed, move unused information to the slower system memory space, effectively increasing the capacity available to the GPU. The corresponding slider determines how much memory gets set aside. As it pertains to Radeon RX Vega 64, AMD exposes an option in its driver called HBCC Memory Segment to allocate system memory to Vega's cache controller.
0 Comments
Leave a Reply. |