swaaye wrote:I tried to classify these chips awhile back and came up with this:
5200/5500 - 2x2
5600/5700 - 4x1
5800/59x0 - 4x2/8x0
59x0 - 16 […]
Show full quote
I tried to classify these chips awhile back and came up with this:
5200/5500 - 2x2
5600/5700 - 4x1
5800/59x0 - 4x2/8x0
59x0 - 16x0 with stencil pass?
AFAIK (based on everything I've read on NV3x) the 5800/5900 are all "8 pipe" variations that can operate as 4x2, 8x1, or 16x0. The 5200-5700 series are "4 pipe" and can operate as 2x2, 4x1, or 8x0 (I'm not 100% certain on this with the 5200/5500, cf what you posted below).
Tech Report also saw behavior from the 5200 that was mirroring what a GF4MX was doing and so they thought maybe 5200 had more in common with NV17 than one might guess from codenames.
nVidia's "official line" seems to be that FX 5200 is CineFX I based (which means no NV1x), but they also do not list it as an Intellisample part. If I had to guess, they probably took the memory interface (and maybe more?) off of the MX for the 5200/5500, just as they did with GF4 Ti for the 5800 (4x32-bit controllers). Both cards have similar memory bandwidth, and it wouldn't be surprising if that was a limiting factor for the FX more than the 4 MX, since the 5200 is supposed to be capable of more computational thruput than the MX, especially when you factor in the shader support.
swaaye wrote:
There might be some scenarios where the bandwidth helps 5900 a lot. Games that are relatively simple, run at high resolution, and with some anti-aliasing added in? Maybe DirectX 7 era games setup like this.
If I remember right it was a flight or driving simulator, so it was probably very fill/bandwidth dependent and the shader processing power on GF6 doesn't count for much. If I come across it again I can link you - it was certainly surprising to see the 5950 performing so well. 🤣
I think Putas also brought up once that we have no idea how efficient NV3x is with bandwidth compared to NV4x so that huge bandwidth on 5900 might be more necessary than it is for say 6600.
According to stuff I've read in the past (and would probably be hard-pressed to find again), NV30 was able to achieve something like 4-5:1 efficiency due to its compression features, and early nV marketing materials will often claim it has "equivalent 48GB/s of memory bandwidth" when comparing it to Radeon 9700. What I'm not sure about is the transition to NV35; I would assume that either the NV35 drops some of those bandwidth saving technologies, or the extra memory bandwidth is largely irrelevant and was included as a marketing feature (so they could say "me too!" with 256-bit memory). I say this because many benchmarks (including some I've done myself) comparing NV30 to NV35 usually don't show dramatic performance differences until you get into shader-heavy applications (where NV35 has a computational advantage).