Slashdot Mirror


Samsung Claims World's First 288Mb Rambus DRAM

Hugo writes "Samsung Electronics announced the completion of development of a 288Mb Direct Rambus® DRAM (RDRAM) component and 576MB Rambus In-line Memory Module (RIMM?) Module. A design rule of 0.17-micron is used. The data processing speed at each pin has been improved to 800Mb per second, so the device can process the equivalent of 6,550 newspaper pages of information per second." Samsung does a *lot* of predicting about future RAM, but seems to be moving right along. Check this story from June '98.

21 of 123 comments (clear)

  1. "Line forms on the left" by Forge · · Score: 2

    Yells the computer store clerk when this things hit the street and regular SDRAM prices take another dive.

    Ahh if only the new BMW would do _that_ to the Corolla I can *almost* afford.

    --
    --= Isn't it surprising how badly I spell ?
  2. A MCSD's opinion by Da+VinMan · · Score: 2

    From what I have seen, the Windows kernel is VERY stable and fast. However, it's basically an extensible design, like a micro-kernel architecture, that is expected to remain stable with a variety of extensions by other companies, mostly in the form of drivers, CODECs, etc. My opinion is that's where Windows stability problems come from. Linux has an advantage here because of the open source aspect and because "core" Linux drivers (i.e. those that get distributed with the mainstream kernel source) tend to be looked at by very knowledgable individuals before being circulated. In the Windows world, anyone can deliver a driver, DLL, what have you and, since the source is never released, many common mistakes may never get fixed, or get fixed only after many users have suffered with the problem.

    Just $0.02 from a MCSD (since 1996).

    --
    Please mod this post only if you think others should/n't read this. I have enough ego^H^H^Hkarma. Thanks!
    1. Re:A MCSD's opinion by JustShootMe · · Score: 2

      OK, this was my understanding: (keep in mind this is what I heard via hearsay and it may bear little to not resemblance to the truth!)

      Sometime ago, the chief coder of VMS, a Dave Cutler (I think) got hired away from DEC to be the chief coder for WNT (notice that WNT is one character away from VMS). It was also my understanding that along with the coder came a bunch of the code for VMS (this is what I heard). They used it in the kernel for the first Windows NT release. But somehow they got caught - they even kept the *comments*.

      So DEC struck a deal with Microsoft - you can keep using our technology *if* you port NT to Alpha.

      Hence a very stable kernel, because it was essentially VMS.

      Then, when 4.0 was released, some yahoos over at MS had the bright idea to start tinkering with the kernel - moving graphics calls into kernel space. IMO, I don't care what the performance gains are, that's a really BAD IDEA. But it was my understanding that the speed gains this created were offset by the instability this change introduced into the kernel. It is a documented fact that MS has been moving many things that arguably shouldn't be there into the kernel, and destabilizing it in the process. A miswrote graphics call shouldn't crash the kernel. But I digress...

      Anyway, this was what I heard and my understanding. Someone knowledgable feel free to correct me. The point I'm trying to make though is that arguably MS *has* been destabilizing their kernel in order to attain nebulous performance gains. I have no doubt that the MS kernel is *reasonably* stable - read just fine for desktop or light load use. But I don't and wouldn't trust it with my mission critical stuff...

      Anyway, this has ended up offtopic...


      If you can't figure out how to mail me, don't.
      --
      For linux tips: http://www.linuxtipsblog.com
  3. Why the weird memory size? by Jerenk · · Score: 2

    Anyone have a technical reason why Samsung is using 288MB instead of 256MB? Looking at their press release doesn't help. I am not familiar enough with RAMBUS to know more...

    0.17 micron seems small. Can they expect to produce enough of this? I thought I read that there are only a few fab plants that can produce 0.18 micron chips - I imagine it must be even smaller 0.17 micron chips.

    RAMBUS - vaporware (or will I be shocked?).

    -- Justin

    --
    Mu. P.S. The address you see is real. =)
    1. Re:Why the weird memory size? by wmono · · Score: 2

      My guess is, it's parity RAM. Eight bits of storage space getting one parity bit makes 256MB + 32MB = 288MB.

    2. Re:Why the weird memory size? by RevRigel · · Score: 4

      My guess would be that it's parity ram. 256 = 32 * 8. 288 = 32 * 9. Extra bit for parity checking and all.

  4. Re:I don't know where you live... by TheBashar · · Score: 2

    Maybe they're talking about the advertising section as well. Takes more space to scan in and save all those pictures of brassiere models.

  5. New Math? by TheBashar · · Score: 2

    From the article:

    "Sixteen 288Mb Direct Rambus® DRAM components can be configured together to create a 576MB module."

    Can someone please explain to me how 16 x 288 = 576? Thanks!

    1. Re:New Math? by TheBashar · · Score: 2

      Missed that darn little "b". Thanks for pointing that out to all who replied.

  6. Re:please explain by QuMa · · Score: 2

    Parity... Basicly, you take the least significant bit of the sum of the other 8 bits (or, to put it differently, you add the 8 data bits together, if it's even the parity bit is 0, else it's 1), and dump it in the parity bit.


    >So they are marketting it as 288 when it can only store 256 of real data?

    Of course they are...

  7. Re:please explain by QuMa · · Score: 2

    Yes, but still, this press release meant to let the public know: look, we've made really cool ram. And they're making it look better than it is by doing it in bits.

  8. Standard units! WOOHOO! by Myself · · Score: 2

    How many bytes of data flow over Niagara Falls in a second? Now THAT's memory bandwidth!

    Would an Empire State Building worth of magnetic core memory come close to one of these RIMMs?

    If you outfitted pirahna with this RAM, would they be able to skeletonize a cow in less than a millifortnight?

    For that matter, how many picoY2Ks of hype does this press release contain?

  9. Standard units of measurement by Dirtside · · Score: 2
    I wasn't aware that a "newspaper page" was a standard unit of measuring data:

    # df
    total newspaper pages: 725580
    newspaper pages used: 15887
    newspaper pages free: 709693


    --- Dirtside | "Spirituality" is the irrational belief in the supernatural

    --
    "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
  10. please explain by Asparfame · · Score: 2
    So that means that technically, they can only store 288 * 8/9 = 256 MB of data, and that 32 MB are there just as "checksum" or something? (How exactly does this work?)

    So they are marketting it as 288 when it can only store 256 of real data?

    --

    There's no reason for a sig here.

  11. Re:288Mb? Bloat away! by JustShootMe · · Score: 2

    I personally don't build kernels to be small, I build them to be functional. I really dislike modular code and on "production" machines I even build the kernels without module support at all. It just makes things easier.

    That being said, I bet you could build them damned small. But you know, I bet the core kernel code for windows NT is small too. It's the stuff they build around it that sucks.

    Windows NT, from what I understand, is basically a modified VMS kernel, at least in 3.1 or 3.51. Notice how the kernel destabilized the further away you got from that release? As I understand it, it's because the Windows coders started to tinker around in the kernel and destabilized it.

    Just my $.02


    If you can't figure out how to mail me, don't.
    --
    For linux tips: http://www.linuxtipsblog.com
  12. Re:Ram technology review by JustShootMe · · Score: 2

    What I don't like about rambus is how they seem to be pushing it not on its merits but because it'll be good for their (Intel's) bottom line. I also don't like the thought of paying at least 4 times as much per megabyte (though that would probably equalize). I like the SDRAM just fine, thanks.

    That being said, it's very heartening that it seems to have almost no support in the industry at this point. Although putting 288mb on a chip isn't a small achievement...


    If you can't figure out how to mail me, don't.
    --
    For linux tips: http://www.linuxtipsblog.com
  13. You've got it right -- latency vs throughput by Anonymous Coward · · Score: 3


    While PC100 SDRAM and 800MHz single-channel RAMBUS have the same theoretical peak rates of throughput, RAMBUS appears to be better at sustaining higher real-life throughput levels. On the other hand, SDRAM's latency is lower -- sometimes *much* lower (60ns vs 120ns) -- and for a large class of applications main memory random-access latency is a more important performance limitation than memory throughput. Just to be fair, there are also many applications (mostly floatingpoint-intensive workstation applications) which benefit more from high throughput than from low latency.
    &nbsp
    On the gripping hand, the growing disparity between the operational rates of memory busses and microprocessors is making latency increasingly important. In the next two years the time spent filling cache from main memory will comprise a significant fraction of total runtime. This paper is several years old, but thusfar the industry is proceeding according to the schedule predicted by its authors:
    The Memory Wall

    One thing to keep in mind when reading this paper is that SDRAM's low sequential access latencies are equivalent, in the context of this paper, to a form of caching. Think of it as extra caching going on in the memory module itself, and use 60ns as the latency of a main memory access (ie, a cache miss).

    One thing that RAMBUS is supposed to do (but thusfar has not) is make processors and motherboards easier and less expensive to build. It is much, much easier to get an 8-bit-wide bus working correctly than a 128-bit-wide bus, and chip manufacturers are having to come up with new and gruesome ways of sinking more IO pins into their products, which is a costly pain in the ass. The PCB real estate consumed by a motherboard's 128-bit-wide bus isn't cheap, either. Whether RAMBUS will ever succeed in delivering on this particular promise remains to be seen.

    -- Guges --

  14. No. It's a scam. by Wakko+Warner · · Score: 3
    It's 8 bits wide instead of the 64 bit width you get for normal SDRAM. RAMBUS can only hit 800 MB/sec, the same throughput as PC100 SDRAM. PC133 SDRAM has it beat by, of course, 33%. Real-world testing puts it either as fast as, slightly slower than, or slightly faster than SDRAM, depending on which site you go to and what day you visit it. Regardless, you won't see much difference at all, but you'll sure pay a lot.

    Don't even start comparing it to DDRAM (double-rate DRAM), which will be appearing soon and which can be produced on the same production line as SDRAM is with minimal retooling. This means, of course, manufacturers will love it.

    RAMBUS is, plain and simple, a scam.

    - A.P.
    --


    "One World, one Web, one Program" - Microsoft promotional ad

    --
    "Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
  15. RIMM? by A4Joy · · Score: 3

    That cracks me up. 'Well, I sent the motherboards in for an upgrade last week and we're still waiting on the RIMM job.'

    Tasteless, yeah, I know... I am so ashamed of myself.

    ---
    Tempfiles fugit.

  16. This just in.. by myconid · · Score: 4

    This just in:
    Samsung has began a new program to help American's afford their new 288Mb Rambus DRAM. We have been informed that Samsung is taking "trade ins" of whole human appendages and key organs. They say that for an arm, or a leg, they will trade a single 288Mb RDRAM. For any major organ, 2 288Mb RDRAM, and for essentail organs, 4 288Mb RDRAM modules.

    --

    SB.
  17. Ram technology review by Scott+McGuire · · Score: 5

    Ars Technica had this link to an article about ram technologies. RAMBUS didn't look so good there.