- Joined
- Nov 4, 2005
- Messages
- 11,988 (1.72/day)
| System Name | Compy 386 |
|---|---|
| Processor | 7800X3D |
| Motherboard | Asus |
| Cooling | Air for now..... |
| Memory | 64 GB DDR5 6400Mhz |
| Video Card(s) | 7900XTX 310 Merc |
| Storage | Samsung 990 2TB, 2 SP 2TB SSDs, 24TB Enterprise drives |
| Display(s) | 55" Samsung 4K HDR |
| Audio Device(s) | ATI HDMI |
| Mouse | Logitech MX518 |
| Keyboard | Razer |
| Software | A lot. |
| Benchmark Scores | Its fast. Enough. |
I know NVlink won't replace memory, it's merely the protocol for interdie communication.AA would probably be one of the postprocessing methods done at the end of rendering a frame.
You can't get off with shared memory like that. You are still going to need a sizable part of assets accessible by both/all GPUs. Any memory far away from GPU is evil and even a fast interconnect like NVLink won't replace local memory. GPUs are very bandwidth-constrained so sharing memory access through something like Zen2's IO die is not likely to work on GPUs at this time. With big HBM cache for each GPU, maybe, but that is effectively still each GPU having its own VRAM
Chiplet design has been the end goal for a while and all the GPU makers have been trying their hand on this. So far, unsuccessfully. As @Apocalypsee already noted - even tiled distribution of work is not new.
I am saying the IO die could handle memory interleaving between two sets of 6GB vram and assign shared and dedicated memory and resources, it's already the same sort of memory management used, but with the ability to share resources with multiple dies, which would also make them a good shared workstation card, allow hardware management of user and resources allocation.
