1. Jan 12th, 2007

    Solid State Disk Changes The Game

    CES came, CES went, and like every year, I ignored it. It might be the size of my apartment, or my checking account, but I don’t have a burning desire to own a TV that’s taller than me. Or to hook it up to a media center that can fit in my pocket. Nor am I fascinated by cell phones with mediocre reception in four different bands! And I already settled the Blu-Ray vs HD-DVD debate by choosing neither one.

    So excuse me for not paying attention. But there was one piece of seriously interesting news. And, ironically, it has less to do with consumer electronics. SanDisk started selling Solid State Disks.

    Solid State Disks (SSD) don’t mind when your notebook loses balance and hits the floor. But even better, they eat up less battery when running, and can quickly suspend to disk instead of suspending to RAM. So what do you do with all this new found battery charge? Pipe it to the radio transmitters: WiFi, Bluetooth, Cellular, WiMax.

    We’re getting one step closer to always-on connectivity, on the desktop and the notebook. It will happen first in executive toys, which explains why SanDisk chose CES to bring us the news.

    When SSD go mainstream, they’ll change the way we use computers. You trade local storage – 32GB is not a lot of space for a modern operating system, music collection and the occasional ripped DVD – for the ability to live in the cloud: to always have access to more information that any one computer can store.

    And, it will change the way your software runs. When there’s little penalty in saving to disk, there’s no reason not to. Your changes are stored as you’re writing the memo, or playing with the spreadsheet. I won’t shed a tear over the loss of the Save button.

    We can almost do it today, we have auto-save that creates a backup in the background every minute or so. But if you crash, you lose your place in the document, the last few keystrokes and all your undo actions. So you still need to commit to a change, to let the software know you’re ready for what may come. That will no longer be necessary.

    But what I’m most excited about is the way it changes our computation ability.

    Every year, like clockwork, hard disks get bigger, faster and cheaper. Yet, we’re still hitting the same wall, the slow speed by which the needle dances from track to track, waiting for the right sector to pass underneath. Relatively, the bigger the hard disk, the slower it can access the data. That’s why we call hard disks the new tape.

    With SSD, the hard disk will literally become the new tape.

    SSD has constant seek time, so it doesn’t matter where the data resides. It’s as efficient streaming a movie as it is collecting records scattered all over the database. SanDisk claims it’s a hundred times faster, but even an order of magnitude is enough to change the rules of the game.

    All of a sudden we can build applications that are smarter by virtue of having more data on tap. We can be more liberal with our reads and writes, expand our queries, use more meta-data.

    It all comes from the simple fact that hardware has to pay for itself. $18 affords you 1GB of SSD (expected to halve every 18 months). You’ll have to pay nearly ten times as much for RAM. Of course, both are considerably more expensive than magnetic media, so video and backup are not the killer-apps for SSD. But video and backup work fine with tapes.

    Think of the way we develop software for servers. You can only afford so much RAM, that’s your upper limit on the amount of data you can process quickly. Disk access is so slow, it’s the first bottleneck you optimize around. You work around the snail-store by sticking to the confines of affordable RAM. You may have 250GB of storage in there, but you’re building the software to live in 4GB or less.

    What if we opened the floodgates? What if you had 2GB of RAM to compute, 32GB of SSD for fast random access, and 250GB of the slow kind. How would that change the way you design, and the kind of features you build?

    Now granted, hardware always improves at least at constant rate, and software expands at the same rate to fill it up. But sudden increases lead to sudden expansion, and sudden expansion comes not from incremental improvements, but innovating new ways we couldn’t afford before.

    Think of what happened when storage became small and cheap enough to fit your music collection in your shirt pocket? Or when bandwidth jumped from fast enough for text to fast enough for video?

    This change will mostly affect the dark code, the plumbing that runs behind the scene, but out of that will come new types of applications we couldn’t imagine a year ago. Or at least I couldn’t, but I’m starting to have some ideas. What would you do with 32GB of fast, durable memory?

    1. Jan 13th, 2007

      Tom

      It’s a really good point Assaf. I’ve seen people talk about SSD for a while, but with a product brought to market at a major trade show things are starting to move.

      I particularlly liked your point about using the gained laptop battery life on wireless. With the ubiquity of wireless protocols now, I can really imagine a situation where we all have big platter disks to dump to. Either at home or in the office but still doing all our processing on a local SSD. Every network gear vendor has a product which will house at least two big platter disks in an enclosure to use as plug and play networked storage. Finally all the pieces seem to be in place.

    2. Jan 13th, 2007

      http://blog.cfrq.net/chk/

      At the other end of the spectrum…

      My internet server goes down every year or two because of hard disk failure. I’m currently running it with a 30Gb drive, which is less than half full.

      What would I do with 32Gb of SSD? replace the dratted rotating disk in my server…

    3. Jan 14th, 2007

      dnl2ba

      It’s not true that bigger disks are slower than smaller disks. In fact, with greater density comes faster reading at the same RPM. Think about it– the read head covers more data per rotation.

      Anyway, I’d love an SSD either as an expansion or as the main drive in an ultraportable like my Fujitsu Q2010. The model I bought has only a 30GB 1.8″ HDD anyway, so what do I mind if SSDs are only 32GB right now?

    4. Jan 14th, 2007

      Name

      Change the grammar please, that’s unprofessional:

      “Your changes are stored as your writing the memo” to
      “Your changes are stored as you’re writing the memo”

      Thanks.

    5. Jan 14th, 2007

      Dru Nelson

      This is old news. There is much room for improvement.

      http://ezine.daemonnews.org/200012/daemonnews200012.pdf

      See TRAM, An old idea forgotten.

    6. Jan 14th, 2007

      Assaf

      @dnl2ba

      To pack more data into the same media size, you increase the density of both sectors and tracks. Increasing sector density improves throughput lineary, but increasing track density doesn’t. You can compensate with faster RPM, but the growth there is not nearly as fast.

      So the density of disks advances faster than their seek time. So disks improve faster to hold more data (e.g. more videos, bigger tables), but not nearly as fast to access it (e.g. quality of video, complexity of queries).

      @dru

      We already have battery backed RAM: a typical notebook can retain its memory image for days without external power. But the price of RAM is too high to replace disk.

    7. Jan 14th, 2007

      tnkgrl

      Beyond SanDisk’s 1,8″ (iPod size) 32 GB ATA SSD there’s also PQI’s 2.5″ (laptop size) 64 GB SATA SSD: http://www.engadget.com/2007/01/11/pqis-64gb-ssd-with-sata-connector-a-worlds-first-twice/

    8. Jan 16th, 2007

      Adam Piotr Żochowski

      CPU has registers, those are fast
      then we have L1 cache,
      then we have L2 cache
      then we have RAM
      then its harddrive (or LAN if its fast enough)

      SSD ‘harddrives’ are sandwitched between RAM and real harddrive. so the data chain becomes

      registers -> l1 -> L2 -> RAM -> SSD -> harddrive

      Now, lets look at the layers. L1/L2/RAM is all transparent to the user, and, more importantly, to the program.

      How do we tell OS to use SSD as extension to our RAM? simply we call it SWAP space, all you do is :

      /dev/??? none swap sw 0 0

      Dont even bother wasting SDD space on partitions, just designate complete SSD as SWAP. For example, your connected SSD becomes /dev/sdc, instead of making primary partition with /dev/sdc1, you can set it to use complete device :”

      /dev/sdc none swap sw 0 0

      cheers

      ps: please, when you change font color change the background as well, and vice-versa. Your textarea/inputs look normal, but on hover you change my default black background to some ivory color. and I end up with white fobts on white background. Its hard to write.without seeing.

    9. Jan 16th, 2007

      Preston L. Bannister { random memes } » Near an inflection point - solid state disk

      [...] Solid state disk is one of those technologies that never seemed to quite arrive. Smaller in storage and (much) more expensive than hard disks, solid state storage has never proved practical outside niche applications. This may be about to change. After spotting an 8GB flash card under $100, we may be near the point where solid state memory can displace hard drives for a substantial number of mainstream applications. Labnotes » Solid State Disk Changes The Game When SSD go mainstream, they’ll change the way we use computers. You trade local storage – 32GB is not a lot of space for a modern operating system, music collection and the occasional ripped DVD – for the ability to live in the cloud: to always have access to more information that any one computer can store. [...]

    10. Jan 20th, 2007

      Post It #5 | tail -f carlo.log

      [...] Solid State Disk Changes The Game [via Simon]: [...]

    11. Apr 22nd, 2007

      Petr Gladkikh

      I’ve always been worrying about durability of these disks and it seems that _everyone_ around avoids speaking one of major limitations of flash disks: number of rewrites is limited to 1e4…1e6 for each block. This of course can be somehow mitigated by background re-mapping of blocks at the driver level.

      What i’ll do with such sorage? Spare it and not write there too often.

      Is this problem already solved? Is there statistics showing that this does not matter (say if a even a heavily used SSD will last more than 5 years)? Or what are the reasons no one speaks about it?

    12. May 31st, 2007

      SSD

      dose anybody know this particular SSD? I saw a review from Korean website, but I can’t read Korean. Someone please help out!
      http://www.acrofan.com/bbs/zboard.php?id=device&page=1&sn1=&divpage=1&sn=off&ss=on&sc=on&select_arrange=headnum&desc=asc&no=100

    Your comment, here ⇓

    Or using OpenID