Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Hey man, you said it. IMO? if it was something they did not know about they would have made a statement to say "We really don't understand why this is happening and are looking into it".
But no. Instead they come along and tell you exactly why it's happening, because basically that's how the 970 uses its VRAM. They then post some benchmarks showing that it's not much worse than a 980....
What's the point of putting on, say, a 7990's box 6gb VRAM ! when we all know that it's really 3x3gb VRAM and you can only use 3gb of it because the other 3gb is just there to make the card run?
It's called marketing my friend. And once you understand that you'd be just as cynical and mistrusting as I am !
So much for 970 any day of the week in all 290 or 970 threads
Yes, but the thing is we kind of know that from the get go, that dual GPU cards RAM dont add, there's nothing implying on the 970x that 500MB of your RAM is dog ****.
Can you do the same as I have done with my GTX 980
1. Use the same clock settings as I am running in GPUZ
2. Use the same bench settings in the pics below
3. Run the benchmark.
If your GTX 970 is working ok you should be looking for a score of 70.55 fps.
Yes, but the thing is we kind of know that from the get go, that dual GPU cards RAM dont add, there's nothing implying on the 970x that 500MB of your RAM is dog ****.
Had they launched it with 3.5gb VRAM no one would have bought it dude. It would then sound like it has far less going on than the 980. What Nvidia wanted people to think was that it was basically a 980 with a few things cut out that when overclocked matches the 980. It was the same with the 670. Hardly any one bought the 680, because IMO the 680 was only really there to make the 670 look like great value.
This is a lesson they learned from Fermi. They were down and out, almost out of business, then they come along with the 460 and *BANG* knock it out of the park. They sold like wildfire because they were cheap.
Since then they've left the kitchen sink well alone and have been making their profits selling lower end stuff for top money.
Pretty much genius, until you get caught lmao
It appears to only affect the 970 series...
Taken from Overclock.net
Quote:
Originally Posted by Serandur View Post
Quote:
Originally Posted by JohnLai View Post
=.= From the Nai's Benchmark, assuming if the allocation is caused by disabled of SMM units, and different bandwidth for each different gpus once Nai's Benchmark memory allocation reaches 2816MiBytes to 3500MiBytes range, I can only assume this is caused by the way SMM units being disabled.
Allow me to elaborate my assumption. As we know, there are four raster engines for GTX 970 and GTX 980.
Each raster engine has four SMM units. GTX 980 has full SMM units for each raster engine, so there are 16 SMM units.
GTX970 is made by disabling 3 of SMM units. What nvidia refused to told us is which one of the raster engine has its SMM unit being disabled.
I found most reviewers simply modified the high level architecture overview of GTX 980 diagram by removing one SMM unit for each three raster engine with one raster engine has four SMM unit intact.
First scenario
What if the first (or the second, third, fourth) raster engine has its 3 SMM units disabled instead of evenly spread across four raster engine?
Second scenario
Or, first raster engine has two SMM units disabled and second raster engine has one SMM unit disabled?
Oh, please do notice the memory controller diagram for each of the raster engine too. >.< If we follow the first scenario, definitely, the raster engine will not be able to make fully use of the memory controller bandwidth.
I agree that this is the most likely explanation, which would mean the issue is hardware-related and cannot be fixed. Here's an illustration of GM204:
** No hotlinking **
http://images.bit-tech.net/content_i...gtx980-17b.jpg
It does seem that each of the four 64-bit memory controllers corresponds with each of the four raster engines and in the same way that the 970's effective pixel fillrate has been demonstrated to be considerably lower than the 980's even though SMM cutting leaves the ROPs fully intact (http://techreport.com/blog/27143/her...an-the-gtx-980), the same situation may apply to bandwidth with Maxwell. However, the issue may be completely independent of which SMMs are cut and may simply relate to how many.
GM206's block diagram demonstrates the same raster engine to memory controller ratio/physical proximity:
http://cdn3.wccftech.com/wp-content/...ck-Diagram.jpg
I expect a cut-down GM206 part and even a GM200 part will exhibit the same issue as a result, it might be intrinsically tied to how Maxwell as an architecture operates. Cut down SMMs -> effectively mess up ROP and memory controller behavior as well as shaders and TMUs. I also don't think there's a chance in hell Nvidia were unaware of this, but I could be wrong.
Quote:
Originally Posted by JohnLai View Post
Yeah, it does seem the driver prioritizes on using 3.5Gb, otherwise the performance impact of using more than that would be too apparent.
But it would depend on how GTX 970 SMM being disabled.
64bit memory controller, total 4 memory controllers = 256 bit memory controller.
Assuming if there are 3 raster engines with each three has one SMM disabled leaving 1 raster engine with 4 SMM intact.
Mathematically ;
16 SMM = 256 bit = 4096 Mb
13 SMM = 208 bit = 3328 Mb
208 bit = effective width after disabling SMM with 256 bit being actual memory controller width.
I could be wrong on this oversimplify calculation. Still worry if one raster engine has three disabled SMM >.<
My 970 was a fantastic buy and given the choice id still go for the 970.
Score was 72.88, but as you can see it wouldn't use all the vRam.
Meh. If something comes out of this then fair play, but if not then meh. My 970 was a fantastic buy and given the choice id still go for the 970.
I was not expecting GPUZ to show 4gb for the 970, this backs up what NVidia are saying that the 970 memory is split 3.5 and 0.5gb with GPUZ showing the 3.5gb part.
What were your minimums like as this will also highlight if the VRAM is holding you back.
72.88 for the average is a good score for a 970.
If it cannot be fixed then the people who upgrade every couple of years who hold onto their cards longer could be seeing more problems down the road as games start to use more memory.
To be honest I dont care about the VRAM thing like some people get all het up about. I have NEVER EVER seen it be a problem when I play games.
The 970 is still a brilliant card for me.