QuadroFx1000 ( NV30GL ) news and pic

[Xmas]

Great...does this mean that to be fair, we're going to have to run benchmarks at several different environmental conditions and lengths of time to get the whole picture?

If that 140 °C number is default, we really don't have to worry about this

I don't think this will have an impact on benchmarks, it's just a security feature like P4's throttling is.

 

[martrox]

Well, guess I could use an FX here tonight..... going down into the 20's (F, not C)... tuff on this Floridians' thin blood......

 

[BenSkywalker]

T2K-

I know your post is a few days old, but I figured someone else would correct your calcs by now-

Let say 1600x1200 MSAA... that's 1,920,000 x 16 = 30,720,000 per channel

So look at this w/ 16bit per channel: 30,720,000 x 8 = 245,760,000 ~ 246MB!!!

1600x1200x32x16= 983,040,000/1024/1024/8= 117.1875MB

That's 32bit color with 16x AA and no compression. Your big error was figuring for Mb, not MB.

 

[OpenGL guy]

1600x1200x32x16= 983,040,000/1024/1024/8= 117.1875MB

That's 32bit color with 16x AA and no compression. Your big error was figuring for Mb, not MB.

Toss in 32-bit Z buffer and that's 234.375 MB.

 

[Doomtrooper]

Great...does this mean that to be fair, we're going to have to run benchmarks at several different environmental conditions and lengths of time to get the whole picture?

If that 140 °C number is default, we really don't have to worry about this

I don't think this will have an impact on benchmarks, it's just a security feature like P4's throttling is.

Issue is that it's clocked at 400 mhz vs 500 mhz.

 

[Xmas]

Great...does this mean that to be fair, we're going to have to run benchmarks at several different environmental conditions and lengths of time to get the whole picture?

If that 140 °C number is default, we really don't have to worry about this

I don't think this will have an impact on benchmarks, it's just a security feature like P4's throttling is.

Issue is that it's clocked at 400 mhz vs 500 mhz.

So what? That QuadroFX also has a slightly more 'conventional' cooler.

 

[Xmas]

1600x1200x32x16= 983,040,000/1024/1024/8= 117.1875MB

That's 32bit color with 16x AA and no compression. Your big error was figuring for Mb, not MB.

Toss in 32-bit Z buffer and that's 234.375 MB.

Toss in a front buffer and another buffer for downsampling or triple buffering and that's 249MiB

 

[Doomtrooper]

Xmas..if there is clock throtling on a lower clocked 400 mhz version...what is it going to be like on a 500 mhz variant...just a observation

 

[Xmas]

Xmas..if there is clock throtling on a lower clocked 400 mhz version...what is it going to be like on a 500 mhz variant...just a observation

Apply the same logic to a P4 3,06 GHz...

 

[Doomtrooper]

Doesn't apply as we don't know exactly what the threshold is, I find 140 Degrees hard to believe.

And I'm not a P4 Fan

 

[Dave H]

Here's a tiny question re: this clock throttling feature:

Why is this user-adjustable? How on earth is the end-user supposed to know at what temperature the GPU will melt down?? Isn't Nvidia supposed to have a better idea of that kind of information?

 

[nggalai]

Great...does this mean that to be fair, we're going to have to run benchmarks at several different environmental conditions and lengths of time to get the whole picture?

How so?

"ambient temperature" is board temperature, not room temperature. Or do you suggest the GFFX comes with an external bluetooth thermometer to install on your desk?

ta,
-Sascha.rb

 

[Evildeus]

Here's a tiny question re: this clock throttling feature:

Why is this user-adjustable? How on earth is the end-user supposed to know at what temperature the GPU will melt down?? Isn't Nvidia supposed to have a better idea of that kind of information?

For overclockers?

 

[Dave H]

For overclockers?

Overclockers don't want their chips to catch fire either. OC'ing a chip to its limits does not mean the limits of its heat dissipation but rather the limits of it being able to complete all the calculations it needs to every clock cycle. Throttling the chip at dangerous temperature levels is not going to steal a single fps from even the most extreme overclocker; all it will do is stop chips from being fried.

(Besides, presumably it will only reach 140 deg. C if the fan fails.)

 

[Tekime]

For overclockers?

Overclockers don't want their chips to catch fire either. OC'ing a chip to its limits does not mean the limits of its heat dissipation but rather the limits of it being able to complete all the calculations it needs to every clock cycle. Throttling the chip at dangerous temperature levels is not going to steal a single fps from even the most extreme overclocker; all it will do is stop chips from being fried.

(Besides, presumably it will only reach 140 deg. C if the fan fails.)

Just a thought: OC'ing a chip means completing all the calculations, AND finding the limitations imposed by heat. I doubt that every single GFFX created will have the same heat threshold, and any serious overclocker is going to want to find that threshold (as opposed to depending on NV's 'best guess' average).

At any rate, just having the ability to change it doesn't mean you have to change it; but having the option to is a good thing for the hardcore OC'ers..