Originally Posted by Luke212
its good engine design to use all available space for caching of data. this is why vram usage tests are a joke, because it cant differentiate the two. what you need to do is artificially limit vram to certain levels and then compare frame rates to see if it makes a difference. if not, then it was never needed.
if you like i can write an application that absorbs a certain amount of vram. say 1gb-5gb in 1gb steps. then you can run your game benchmarks and see just how much a difference it makes to your fps.
I'm not much of a gamer, 2Gb of memory is still more than I ever use.
Just thinking of the threads where guys ask 'is 3Gb enough?' & seeing the replies of 'no, I'm seeing 3.5Gb memory usage' from one guy & 'I'm running fine with 2Gb, 3Gb is plenty' from another.
A bit more clarity between allocated & used memory would be helpful for some.
Originally Posted by Jpmboy
Just hooked this into the waterloop on the bench rig... 10 min loop of valley at 4K (1254/6389, 1.3V) never exceeded 35C on the 2 titans. One slow 180 fan at the base or passive. Incredible cooling capacity. 4x480 copper tube rads with Alu fins.Warning: Spoiler! (Click to show)
That is quite the tower of rad! Just have to feed the tubes through that window in the cold weather, & all set for some benching!
Have to watch the straight distilled water though, I usually have some antifreeze in so it doesn't get sludgy in cold temps.