Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Hardware

Memory Timings and Memory Bandwidth Explained 6

Gundeep Hora writes "We have just published our recent articles that explain system memory bandwidth and timings. These two are two of the most confused topics and our very own Aubrey Barrington has used his expertise to come up with in-depth yet simple articles that you easily follow. Our Memory Timings article can be found here AND our Memory Bandwidth article can be found here."
This discussion has been archived. No new comments can be posted.

Memory Timings and Memory Bandwidth Explained

Comments Filter:
  • Okay guys (Score:1, Offtopic)

    by sulli ( 195030 ) *
    WTF is with the bizarre color scheme for IT? Was the Games section too easy on the eyes or something?
    • It's all a clever scheme to force everyone back to the front page, I think, so the editors can get 'back' to reading the stories to check for dupes. Seriously, these are bad. I could handle games, BSD, and now this tan thing. Ow.

      At least it's not the purple/yellow apache, right?

      Just keep it green, eh slashdot? You had it right with the apple theme. YRO isn't bad, but tan gradient? No.

  • Not the best article (Score:4, Informative)

    by rapjo ( 211658 ) on Tuesday July 27, 2004 @01:31PM (#9814154)
    This article wasn't really all that great; older articles and memory roundups and anandtech.com and tomshardware.com have done a much better job of explaining CAS speeds and how they affect you.
    • by elmegil ( 12001 )
      Not all that great? It doesn't explain a damn thing, it just dives into the middle of stuff assuming you already know half of it, and starts talking about how the last two of a string of 5 numbers used to rate memory performance are usually misinterpreted.

      Hello, I was looking for an "explanation" of "memory timings", which includes those first three numbers!

  • I'd suggest checking out the "Technical Blackpapers" over at arstechnica for a much better look at memory timings, latency, and bandwidth.

    http://arstechnica.com/ [arstechnica.com]

Single tasking: Just Say No.

Working...