Kuntz... normally I would just delete posts of this inflamatory nature... but honestly, you have taken this one step too far. Insulting my education, belittling my career, and now telling me latency is measured in Hz? ARE YOU OUT OF YOUR MIND?!
First off... the statements made in that RAM guide are correct, albeit vague. In an attempt to make it more viable for average readers, one must use layman. Sorry, but I am not about to go into the specifics of memory timings and operations for the tech area of a Guild Wars forum. I have better things to do with my time, and far far more important things to deal with. Most people wouldn't even bother to read it, muchless understand it. I am glad that you, took the time to read up on exactly how it works.
However, latency is always measured in ns, not Hz. The two are inherently linked, I wouldn't dare dispute that, but the standardized measurement for latency isn't clock cycles, it is nanoseconds.
Timings across a parallel circuit and a complex circuit are ALWAYS measured in Hz. This will never change. The CAS and RAS are set as clock cycles, and of course speed makes a difference, as it does with total theoretical bandwidth. Clock speed affects all numbers, within a given cell, as that would determine the disparity between low end and high end RAM. You are overcomplicating a generic blanket statement, which is very unwise to do.
Timings =/= Latency. Latency is measured in units of time, timings are measured in cycles (Hertz). I never confused the two. I did use the wrong notations at one point (which is where I can see where the confusion came from regarding this whole issue) It is rather apparent though, if you aren't trying to gun me down reading through it, that timings and latency are separate but related terms in the guide.
Quote:
|
Originally Posted by Rahja the Thief
The Latency of a module of RAM is determined by its TIMINGS.
|
Do you know the definition of determined?
Of course, you neglected to read in context, as I clearly stated just below that...
Quote:
|
Originally Posted by Rahja the Thief
CAS Latency (CL) is the most widely understood number. However, do not be fooled by it. Slightly higher CAS on a much higher speed RAM is a good thing.
|
Now why on earth would I suggest that if I meant CAS is directly measured in nanoseconds? Speed would have no bearing if that was what was intended by the layman statements, now would it?
Oh, but thanks for pointing that out and trying to pick out a statement that suited your purposes... Gee, how nice. Feel free to find more of my posts with layman statements that can be removed and taken out of context. I'm sure it will be a valuable use of your time.
Kuntz, you are not keeping in mind a few simple things...
Because there is no additional charge being applied to the wiring leading to graphics cards, and there will be some (dependent on area and environment this can be very low or high) EM and ES interference, this can greatly affect total current (Amperes) The wattage of a PSU is irrelevant, as voltage is in a constant state of flux (ala Amperes in relation or volts and watts, OMG physics!)
This would, again, affect on wire and at gate current. I'm sorry, but I doubt you understand how forward gates and conversion work in processors, as most people don't (it isn't exactly something you can understand by reading and citing Wiki...)
But, in short, energy is lost through each medium it passes through. This electron loss in a processor is known as "leakage". DiELG (Dielectric Gate) leakage is the most common cause for excess heat in a processor of any type. With elevated iL5 gate leakage in the GT200 rev0 chips, this can be seen as power loss.
Again... following me here? Coupled with a driver flaw that is currently being worked on (that is processing very large texture files and/or small texture files out of a large file) [in this case, the gw.dat is an EXCELLENT example], power draw will be elevated, but current must remain stable. If there is ANY issue with current (which isn't pull, as you are citing... pull is wattage, which is VERY different), the card will be forced to throttle to pass the texture files through. Overly simplified, yes; correct nevertheless.
As for my position at nVidia, I am a Senior Process Design and Physical Design "Engineer". I use the term engineer loosely, as it isn't engineering in the traditional sense, but mainly dealing with process design and sampling, most specifically VSLI design and implementation. Don't deface me please... But the good news for you is!!! I won't be working for NV after October, as I am heading over to TSMC as a Jr. Process Engineer (almost the same job as NV, but more room for career advancement) So then, I guess I won't have claim to the NV throne. You try to glorify my position, but fail to realize that I have the same job that 90+ others do, in this company alone.
The fact is...
Quote:
|
Originally Posted by Malician
Rahja, if the Corsair PSU needs to produce over twice of the GTX 260's TDP to run just that card capably, the card is so beyond defective it would've never been allowed out of nVidia's testing labs. To suggest otherwise is a vicious insult against a company I've gladly purchased the following from
|
The Corsair PSU doesn't need to produce twice of anything. There are so many factors that play into at the wire current, and without detailed power specifics, it is hard to tell.
If you want, we can chalk this up to a driver issue and call it a day. The driver issue is (in all likelyhood) presenting itself, and that PSU isn't delivering enough current after conversion and e- inversion to correctly power the GTX260. The card itself isn't terribly flawed, it is within operational parameters.
The multiplicative issues that present themselves is the issue, not one or the other. You cannot simply pick and choose one possible issue. In all likelyhood, this is a driver/power/current issue; a culminated effect so to speak.
And Kuntz... I use my position at nVidia to help people on these forums with hardware related issues. My expertise has helped many, and that is why people trust my opinion. They don't blindly take my advice; they take it because it has been proven effective over the course of 2+ years.
Instead of bashing me and trying to find layman, simplified statements to prove me wrong, why don't you post on the merits of your background in electrical physics, and actually provide me proof that Ohm and Kirchhoff are wrong... Kirchhoff's two laws alone prove that my logic is sound... enlighten yourself before you deface me.
You are taking this way too personally, and I will not stand for any more flaming. If you want to continue this argument, do so in a non inflammatory manner. Provide evidence aside from total energy pull (wattage) that supports your argument. Wattage means nothing in relation to current needed to overcome a driver flaw (that again, is being corrected). Trace leakage, gate leakage, latent loss, electron inversion, converts, etc all play into total power. If there are enough flaws, the current will become instable/too low to compensate for this driver issue, resulting in performance issues.
Sorry, this is the way of things Kuntz. I am but the messenger, not the creator.

But thanks for pointing out the notation issues. I just went ahead and removed the ns from those, as it was totally unintentional. I do make mistakes when posting 3 page essays, sorry. As you clearly have shown, I do make mistakes from time to time in my posts, especially when the original version of said posts are made at 01:49, 8th Jul 2008 (That's nearly 2am) So again, I made a notation error on numbers (and it wasn't just on timings after reading through it). I went ahead and corrected the errors that I found in the post just for you. I am human, I do make mistakes, but my knowledge on the subject is sound.