VRAM technology implications.
This “question” is NOT intended to drag the legal aspects of “marketing truths” into the discussion, so much as to review the GTX-970 hardware as it really is, and we know that now, and what it means.
-
I don’t see too much in the way of “truthful” technical answers to the current hardware configuration. No, I don’t know the exact performance truth other than my RECENTLY purchased GTX-970 works extremely well.
-
Can people who KNOW the right answers chime-in? DO NOT comment on the darn marketing goof, go elsewhere, please. I'm going to sit back and learn, so don't expect responses per say. I can't listen with my mouth open. I want to know the VRAM's configuration limits.
- My AMD 6870 ran with I Gig VRAM at @ 1080P on a 24” LCD with a single notch down or two on most games and was never, "a stuttering unplayable mess”. Why not, as it certainly hit the 1 Gig VRAM ceiling?
- When a card does hit the VRAM ceiling, it seems ANY card forced to go to the system RAM will see a performance hit, although I don’t see this on my AMD 6870 @ 1080P. The GTX-970, and I see it as a 3.5 Gig card with a “soft” hit to the last 0.512 Gig verses a hard hit to system memory above 3.5 Gig. How is this cache technology a performance issue, really? It seems the best solution with this GPU architecture cut-down from the GTX-980 to design in a soft hit and use this memory, than to make the card 3.5 Gig and delete it. You can CHANGE the quality setting to avoid the above 3.5 Gig hit if you like, or, as we do with current “full speed” cards, adjust to avoid the hit to system memory at all.
- In SLI, you only see the memory from the master controller card, so you get 4 Gig even with two GTX-980. And, those using SLI seem to want to run two or three monitors with ½ to 1/3 the single monitor VRAM. These card’s aren’t magic, and you will see VRAM limitations not apparent on single monitor solutions, requiring reduced quality setting. The 980 will hit the VRAM limit and then turn into a “stuttering unplayable mess”, right? OK, the 970 does so slightly under the 980, but where’s the beef in this argument for the price of the card? The 970 is $200.00 cheaper, so WHY would it NOT have limitations not seen in the 980?
- Future proof? Me, I see this as crazy. I buy for TODAY as four or five years from now, even if I had 16 Gig of VRAM, the GPU will be so much different that my “future proof” card will be obsolete. I KNOW that as games go forward I’ll also adjust features to suit. I see no real reason to STOP GPU development so your 16 Gig of 2015 VRAM is good in the year 2020, as though that's the only progress to be made the next 5 years. Do you seriously believe this future proof issue? High-end hobbyists will ditch a 980 in a heartbeat for one significant GPU change VRAM be damned.
- These video cards have THOUSANDS of specifications not on the box. Is THAT a conspiracy to performance? No, the end game (pun intended) is the overall performance to game play. THAT is what I looked at, and NOT a spec in and of itself. I use the card, not a spec. How is the current tested cards performance not accurate to tested data?
-
So, the BIG question is, is a 3.5 Gig card with a soft hit to .512 Gig local cache and THEN to system RAM worse than a 3.5 Gig card that hits system RAM straight away?
-
I can’t see the logic that the latter is better than the former. And, about every card out there except the GTX-970 hit system memory right after the VRAM limit. To avoid the memory latency, you need to reduce some settings, right? I see no complaints about that. My 1 Gig 6870 surely would have seen the issue…and I don’t see, “an unplayable stuttering mess”. It was amazingly good, actually, for a four+ year old card.
-
So in the end, it seems you have a great 3.5 Gig card that needs maybe a tweak or so of visuals to see good game play just before you might need them on the 980. How is that not expected for $200.00 less? How does a soft local .512 cache make the GTX-870 a bad card? What is the “problem” with the “feature” from a pure technical standpoint?
OK, chew me up.
This “question” is NOT intended to drag the legal aspects of “marketing truths” into the discussion, so much as to review the GTX-970 hardware as it really is, and we know that now, and what it means.
-
I don’t see too much in the way of “truthful” technical answers to the current hardware configuration. No, I don’t know the exact performance truth other than my RECENTLY purchased GTX-970 works extremely well.
-
Can people who KNOW the right answers chime-in? DO NOT comment on the darn marketing goof, go elsewhere, please. I'm going to sit back and learn, so don't expect responses per say. I can't listen with my mouth open. I want to know the VRAM's configuration limits.
- My AMD 6870 ran with I Gig VRAM at @ 1080P on a 24” LCD with a single notch down or two on most games and was never, "a stuttering unplayable mess”. Why not, as it certainly hit the 1 Gig VRAM ceiling?
- When a card does hit the VRAM ceiling, it seems ANY card forced to go to the system RAM will see a performance hit, although I don’t see this on my AMD 6870 @ 1080P. The GTX-970, and I see it as a 3.5 Gig card with a “soft” hit to the last 0.512 Gig verses a hard hit to system memory above 3.5 Gig. How is this cache technology a performance issue, really? It seems the best solution with this GPU architecture cut-down from the GTX-980 to design in a soft hit and use this memory, than to make the card 3.5 Gig and delete it. You can CHANGE the quality setting to avoid the above 3.5 Gig hit if you like, or, as we do with current “full speed” cards, adjust to avoid the hit to system memory at all.
- In SLI, you only see the memory from the master controller card, so you get 4 Gig even with two GTX-980. And, those using SLI seem to want to run two or three monitors with ½ to 1/3 the single monitor VRAM. These card’s aren’t magic, and you will see VRAM limitations not apparent on single monitor solutions, requiring reduced quality setting. The 980 will hit the VRAM limit and then turn into a “stuttering unplayable mess”, right? OK, the 970 does so slightly under the 980, but where’s the beef in this argument for the price of the card? The 970 is $200.00 cheaper, so WHY would it NOT have limitations not seen in the 980?
- Future proof? Me, I see this as crazy. I buy for TODAY as four or five years from now, even if I had 16 Gig of VRAM, the GPU will be so much different that my “future proof” card will be obsolete. I KNOW that as games go forward I’ll also adjust features to suit. I see no real reason to STOP GPU development so your 16 Gig of 2015 VRAM is good in the year 2020, as though that's the only progress to be made the next 5 years. Do you seriously believe this future proof issue? High-end hobbyists will ditch a 980 in a heartbeat for one significant GPU change VRAM be damned.
- These video cards have THOUSANDS of specifications not on the box. Is THAT a conspiracy to performance? No, the end game (pun intended) is the overall performance to game play. THAT is what I looked at, and NOT a spec in and of itself. I use the card, not a spec. How is the current tested cards performance not accurate to tested data?
-
So, the BIG question is, is a 3.5 Gig card with a soft hit to .512 Gig local cache and THEN to system RAM worse than a 3.5 Gig card that hits system RAM straight away?
-
I can’t see the logic that the latter is better than the former. And, about every card out there except the GTX-970 hit system memory right after the VRAM limit. To avoid the memory latency, you need to reduce some settings, right? I see no complaints about that. My 1 Gig 6870 surely would have seen the issue…and I don’t see, “an unplayable stuttering mess”. It was amazingly good, actually, for a four+ year old card.
-
So in the end, it seems you have a great 3.5 Gig card that needs maybe a tweak or so of visuals to see good game play just before you might need them on the 980. How is that not expected for $200.00 less? How does a soft local .512 cache make the GTX-870 a bad card? What is the “problem” with the “feature” from a pure technical standpoint?
OK, chew me up.