Slashdot Mirror


Performance Showdown - SSDs vs. HDDs

Lucas123 writes "Computerworld compared four disks, two popular solid state drives and two Seagate mechanical drives, for read/write performance, bootup speed, CPU utilization and other metrics. The question asked by the reviewer is whether it's worth spending an additional $550 for a SSD in your PC/laptop or to plunk down the extra $1,300 for an SSD-equipped MacBook Air? The answer is a resounding No. From the story: "Neither of the SSDs fared very well when having data copied to them. Crucial (SSD) needed 243 seconds and Ridata (SSD) took 264.5 seconds. The Momentus and Barracuda hard drives shaved nearly a full minute from those times at 185 seconds. In the other direction, copying the data from the drives, Crucial sprinted ahead at 130.7 seconds, but the mechanical Momentus drive wasn't far behind at 144.7 seconds."

259 comments

  1. w00t! by Anonymous Coward · · Score: 0, Funny

    First post?

    And this was on a standard 4400RPM drive in a ThinkPad.... not that that would affect posting to a web page...

    1. Re:w00t! by mrsteveman1 · · Score: 1

      Now all you have to do is cover up the fact that he was ever here at all

  2. bad test by Werrismys · · Score: 5, Insightful

    In typical use most of the time is spent seeking, not just reading or writing sequential blocks. The Windows XP disk IO is especially brain damaged in this regard (does not even try to order or prioritize disk I/O). Copying DVD images from one drive another is not typical use case.

    --
    'Once scientists, even the dim-witted social scientists, get muzzled, the Western Civilization is finished.' - oldhack
    1. Re:bad test by fricc · · Score: 1

      That was my reaction too, big, long donkey ears for the reviewer...

    2. Re:bad test by SanityInAnarchy · · Score: 4, Interesting

      Consider, also, that when you're doing anything other than the contrived "copy from one device to another"... HD-DVD has a minimum guaranteed throughput of something like 30 mbits, Blu-Ray needs 50. It looks like the worst numbers on the solid state devices were still at least some 30 megabytes per second, meaning you could play five Blu-Ray movies at once.

      Skimming the article, it seems very likely that the person responsible has read just enough to be dangerous (they know the physics of why seeking is slow), but not enough to have a clue what kind of behavior would trigger seeking. The one measure was boot time, during which they acknowledge that Vista does a bunch of background stuff after boot, but don't measure it.

      He did get one thing right, though -- they are not exactly living up to their potential. For one thing, there are filesystems explicitly designed for flash media, but you need to actually access it as flash (and the filesystem does its own wear leveling) -- these things pretend to be a hard disk, and are running filesystems optimized for a hard disk, so the results are not going to be at all what they could be.

      --
      Don't thank God, thank a doctor!
    3. Re:bad test by peipas · · Score: 1

      Anecdotally, I have a 32 GB SSD in my Dell M1330. I got stuck with Vista with this machine, but in its "User Experience" rating I get a 5.8 for hard drive. The scale is based on 5.0 being the fastest available at Vista's release. I assume "fastest" refers to consumer machines, but have conventional hard drives somehow become that much more efficient all of a sudden that they meet or exceed this performance?

    4. Re:bad test by ThePhilips · · Score: 4, Interesting

      XP IO subsystem is pretty OK.

      The problem with SSD is that flash based storage has much much higher block size.

      While conventional HDDs have block size 512 bytes, actual SSDs have block size of 64 kilobytes.

      Not only Flashes write relatively slow, but if file system has e.g. cluster size of 8K, every write to it in worst case would also (re)write redundantly 64K-8K=56K.

      Test is realistic - if you want to see how bad most applications can be with SSDs. But that's going to change with SSD becoming more and more common place.

      If they really wanted to test SSD performance they would have taken Linux with jffs2 or newer logfs. Though this two have their own problems.

      --
      All hope abandon ye who enter here.
    5. Re:bad test by Anonymous Coward · · Score: 0

      Here's my real world result:

      after 1 month, I switched the SSD back to an HDD because the performance of cached mode Outlook absolutely stunk on the SSD. Dell Latitude D630.

    6. Re:bad test by Anonymous Coward · · Score: 0

      A WD Raptor will achieve a 5.9 on the Vista rating. Not that it means ANYTHING in the long run heh.

    7. Re:bad test by Anonymous Coward · · Score: 1, Informative

      A few details:

      In fact MLC NAND (erase) block size is more likely 256 kilobytes.

      JFFS2 does not scale above about 1 gigabyte, and linux (MTD) does not currently support more than 4 gigabyte flash anyway.

      LogFS is not main line and is not ready yet.

      There is also UBIFS.

      Conventional wisdom is that SSDs are better than flash file systems because they allow the use of existing tools (block structured file systems), and are cheaper because the technology (think USB sticks) is already used so much. However it is not clear that proposition has ever really been put to the test.

    8. Re:bad test by Impy+the+Impiuos+Imp · · Score: 0, Offtopic

      My reaction was:

      > Performance Showdown - SSDs vs. HDDs

      There's something more badass than a Super Star Destroyer? SWEET JESUS! Hyper Death Destroyers, a 121 mile long monstrosity that can hold a SSD in it's bay! Actually visible side-by-side of a Death Star! Big enough to hold a true planet destroying ray, although it must take over 12 hours to recharge. It can, however, recharge to capital-ship busting level in 39.3 seconds.

      I think this was in that novel where Leia and Luke's daughter has her mind wiped and her face altered, and she accidently makes love to Leia.

      --
      (-1: Post disagrees with my already-settled worldview) is not a valid mod option.
    9. Re:bad test by Dirtside · · Score: 2, Funny

      meaning you could play five Blu-Ray movies at once
      I think someone's just invented a new metric unit for measuring bandwidth!
      --
      "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
    10. Re:bad test by Anonymous Coward · · Score: 1, Informative

      > Not only Flashes write relatively slow, but if file system has e.g. cluster size of 8K, every write to it in worst case would also (re)write redundantly 64K-8K=56K.

      Dude, this isn't how they work at all. If you write 8K, you write 8K. Flash translation layers would carve up the larger sectors into smaller ones. -1 for the people who modded this up.

    11. Re:bad test by frieko · · Score: 1

      Wouldn't a 64kb hardware cache solve this problem?

    12. Re:bad test by Anonymous Coward · · Score: 1, Interesting

      Wrong. Writing to flash requires erasing a block. The erase block size of a typical device is 128K. If I only write 8K, what is this translation layer going to do? Sit and wait until more writes come through? What happens when I shut the system off?

    13. Re:bad test by kesuki · · Score: 1

      SSDs are using NAND memory not NOR memory so you are wrong. NAND memory reads like traditional block devices. Compact Flash was the only device based on NOR memory, and is no longer used widely, and they eventually switched to NAND memory on CF, since the controller is in the chip this was easy to do.

      http://en.wikipedia.org/wiki/Flash_memory
      "Toshiba announced NAND flash at ISSCC in 1989. It has faster erase and write times, and requires a smaller chip area per cell, thus allowing greater storage densities and lower costs per bit than NOR flash; it also has up to ten times the endurance of NOR flash. However, the I/O interface of NAND flash does not provide a random-access external address bus. Rather, data must be read on a block-wise basis, with typical block sizes of hundreds to thousands of bits. This made NAND flash unsuitable as a drop-in replacement for program ROM since most microprocessors and microcontrollers required byte-level random access. In this regard NAND flash is similar to other secondary storage devices such as hard disks and optical media, and is thus very suitable for use in mass-storage devices such as memory cards. The first NAND-based removable media format was SmartMedia, and many others have followed, including MultiMediaCard, Secure Digital, Memory Stick and xD-Picture Card."

      since NAND memory reads and writes like a block device, the only way for a SSD drive to increase its speed is by massively parallel read/write functionality, and since SSD drives are the only massively parallel source of data other than a very large super computer, or a network connection to millions of computers, there is little or no reason to design SSD memory to be massively parallel. i think normally ever 512 blocks has it's own shared read/write device, so sequential writes are horribly slow, since you have to write 512 blocks in a row, for each sequential write, now if you design a test bed where you can read 512 sections of 512 blocks in parallel (either from RAM, across a network, etc) you would essentially have a device that could read/write massively parallel blocks in a a much shorter time than any sequential block device, basically you'd have to RAID array a massive number of HDDs to get the same throughput, but normal SSDs aren't designed to be massively parallel, because most users need sequential throughput, and only server farms etc need massively parallel data streams..

      and for server farms, the read/write limitations of SSD make it an unattractive alternative to conventional HDDs, however SSDs might be a good fit for supercomputers that have to do a lot of processing on a small amount of data, like weather prediction etc. at least, if they were designed to be massively parallel, and could thus be essentially a raid array of hundreds or thousands flash memory chips, instead of a single block device consisting of many many flash memory chips

    14. Re:bad test by ThePhilips · · Score: 1

      As was pointed in sibling comment - No. There are all kinds of problem like e.g. sudden system power off. Many people (me included) would be surprised if file sent to disk an hour ago disappears after crash.

      This is general problem of flashes: as they try internally improve write performance, block size grew very large.

      Only solution: complete redesign of file systems to accommodate such block-sizes. And even that will not solve problem, since most writes from most desktop applications to disks are small. File download/upload, movie encoding/decoding and other batch-like workloads would be fine even with current file systems since they write huge amounts of data thus suffer less from large block size.

      Or probably they can come up with flashes which have smaller block-sizes. That would be much much easier. And from usual inertness of industry I guess they'd rather invent new flash memory than stop using FAT...

      --
      All hope abandon ye who enter here.
    15. Re:bad test by frieko · · Score: 1

      Right, except that HDD's already have caches and they manage okay. So why not SSD's? You would only need to cache 2 or 4 blocks to eliminate most of the redundant writing.

    16. Re:bad test by Anonymous Coward · · Score: 0

      XP IO subsystem is pretty OK. No it fairly well sucks. Linear I/O is fine but it doesn't do block sorting or anything to reduce the time spent seeking.

      The problem with SSD is that flash based storage has much much higher block size.

      While conventional HDDs have block size 512 bytes, actual SSDs have block size of 64 kilobytes.

      Not only Flashes write relatively slow, but if file system has e.g. cluster size of 8K, every write to it in worst case would also (re)write redundantly 64K-8K=56K. That is a shame 8-). It'd be interesting to know if the flash device, or I/O system for either Linux or Windows, is aware of physical block size and coalesces writes (I know this happens for some RAID devices, so it's possible.)

      Test is realistic - if you want to see how bad most applications can be with SSDs. But that's going to change with SSD becoming more and more common place. No it's not. If you're streaming one file to or from the device, while doing absolutely nothing else, it's realistic. That's not typical system usage -- Windows or Linux, the disk tends to thrash away while loading apps and booting, which is typically what people are doing with the disk (let alone doing other stuff WHILE a video is playing).

      If they really wanted to test SSD performance they would have taken Linux with jffs2 or newer logfs. Though this two have their own problems. That would be interesting.
    17. Re:bad test by dgatwood · · Score: 1

      Parent is correct, though I'm not sure about the actual numbers. If your OS is smart enough to know with certainty that no data resides in the remaining parts of that larger physical block, then it can avoid doing an erase cycle for every write. Otherwise, if you write data in units smaller than the physical block size, the flash controller will be erasing and rewriting the whole erase block many times.

      Fortunately, most OSes try to reorder/cluster I/O into large packets to the extent that it is possible to do so, which mitigates this problem to a great extent, but not completely.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    18. Re:bad test by dgatwood · · Score: 1

      Actually, I'm going to correct myself. With wear leveling, chances are, it will be remapping the entire erase block and erasing several different physical blocks a much smaller number of times each.... :-)

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    19. Re:bad test by code4fun · · Score: 1

      Flash can be configured with smaller block size. In general, they are higher block size. If you buy flash chips direct from the vendor, you can tailor it for your application. They make, for example, compact flash that are tuned for a lot of small files. When buying flash from a 3rd party vendor (i.e. suppliers that buy parts from the cheapest supplier), then your mileage may vary.

    20. Re:bad test by TheRaven64 · · Score: 1

      If you want a stable log-structured filesystem, you might try NetBSD. LFS was first implemented for 4.2BSD, as I recall (it might have been 4.4BSD), but it's bit-rotted over the last decade or so. Last release, someone tidied up the LFS implementation in NetBSD to match the newer VFS interfaces. I wouldn't be surprised if NetBSD with LFS performs very nicely on a portable with a flash disk.

      --
      I am TheRaven on Soylent News
    21. Re:bad test by complete+loony · · Score: 1

      4,666 files and folders (a total of 8.05GB) ... I used the same secondary drive as source and destination in all cases. It doesn't look like he only tested large sequential blocks, but I wonder where the real bottleneck was since he used the same destination drive for each test.
      --
      09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
    22. Re:bad test by timeOday · · Score: 1

      Though I agree with your criticisms of this test, I cannot for the life of me figure out why they don't make SSDs with fantastic sustained read/write speed. Seems like it should be easy to increase parallelism to almost any degree desired. It's not like a hard drive where you can only align 1 head with a track at once.

    23. Re:bad test by qopax · · Score: 1

      "The scale of the Windows Experience Index ranges from 1.0 to 5.9." http://www.microsoft.com/windows/products/windowsvista/buyorupgrade/experienceindex.mspx

      --
      I pwn this comment. "The Fine Print" says so.
    24. Re:bad test by afidel · · Score: 1

      Driving more write pins cost electricity and causes heat, both things that are often to be avoided when you are using flash.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    25. Re:bad test by afidel · · Score: 1

      NTFS already supports large cluster sizes up to 64K so it isn't a problem on Windows. I assume most modern FS's have variable cluster size support.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    26. Re:bad test by SanityInAnarchy · · Score: 1

      However, the I/O interface of NAND flash does not provide a random-access external address bus. Rather, data must be read on a block-wise basis, with typical block sizes of hundreds to thousands of bits. In other words, it can seek instantly, but only in 1k chunks. Got it.

      Why is that a problem? Are there some filesystems that actually will typically read less than 1k at a time? For anything?

      the only way for a SSD drive to increase its speed is by massively parallel read/write functionality Which would still be a good thing, IMHO -- as long as it's not possible to, say, slurp a gig into RAM as fast as the RAM can go, it could be better.

      only server farms etc need massively parallel data streams.. It still would be useful for said server farms.

      And it still would be useful for the desktop. It would require a little OS work, but consider -- even if the only application is, say, insanely fast hibernate/resume, that's still a win.

      and for server farms, the read/write limitations of SSD make it an unattractive alternative to conventional HDDs I'm guessing this is, again, largely due to applications and filesystems designed with magnetic spinning platters in mind.

      If a server farm wants a lot of sequential data, it doesn't generally need to be fast. If it wants a lot of data RIGHT NOW, that means you just got a lot more popular, and that data is very likely scattered all over the disk -- thus, it would make a lot of sense to get it all in parallel.

      That said, I've never actually had a raw flash device of any kind to play with. I always wanted to try jffs2, but compactflash just pretended to be a hard drive.
      --
      Don't thank God, thank a doctor!
    27. Re:bad test by SanityInAnarchy · · Score: 1

      The hardware guy seems to have come up with another, perfectly reasonable explanation...

      The problem I see is that applications, OSes, and filesystems are all designed for sequential access. I would love to see something with incredible sustained read/write speed, but I suspect that would require the OS/application actually asking for bigger chunks of the file at once.

      --
      Don't thank God, thank a doctor!
    28. Re:bad test by WindShadow · · Score: 1

      The important advantages of solid state drives are faster seek, less noise, faster "spin up" time on power up, and lower power when not in use. Of these, none was discussed in the article, only seek time showed in the tables.

    29. Re:bad test by msromike · · Score: 1

      I still prefer the tried and true loc/sec (libraries of congress per second.)

  3. Untested performance... by smitty97 · · Score: 4, Interesting

    Unfortunately there's no comparisons of battery life and speed tests with fragmented files.

    --
    mod me funny
    1. Re:Untested performance... by Ethanol-fueled · · Score: 3, Interesting

      ...And the picture won't be complete until we have real-world failure data for the solid-state drives.

    2. Re:Untested performance... by MightyYar · · Score: 1

      But does this justify the extra money... no. That is one thing that cannot be tested - the value of better battery life and faster seek times is subjective. The market will make the best test of whether these things are worth the price.
      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    3. Re:Untested performance... by Jeff+DeMaagd · · Score: 1

      Unfortunately there's no comparisons of battery life and speed tests with fragmented files.

      Is file fragmentation really that big of a problem?

      I know at one time I used to defragment a lot, but the difference has always been negligible for me. I only did it with the thought of keeping it "in tune", but even once a year doesn't make much apparent difference in computer performance.

    4. Re:Untested performance... by Smidge204 · · Score: 1

      Well the whole point of the test would be to prove there IS better battery life and faster seek times - objectively.

      If objective tests show no real advantage, then any subjective improvement in value is basically self-delusion... probably in an attempt to justify the extra cost to yourself.

      If the test DO show an improvement, then I agree it is more up to the customer to determine if the extra cost is worth the extra performance.
      =Smidge=

    5. Re:Untested performance... by plague3106 · · Score: 2, Interesting

      Well, if it takes a full minute more for the SSD vs. the HDD, you may lose any battery savings... since you're powering the SSD for more than one minute.

    6. Re:Untested performance... by MightyYar · · Score: 1

      That may well be, though I can't think of the last time I was on an airplane copying a 4 GB DVD image :)

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    7. Re:Untested performance... by Anonymous Coward · · Score: 0

      In my case it is a slight problem. A sequential read would be as low as 3megs/s for a very fragmented file and 60megs/s unfragmented.
      Among the many ways to get around this problem is a constant low seek time.
      A filesystem that supported large extents would also fix it. Maybe I should switch to JFS.

    8. Re:Untested performance... by TheRaven64 · · Score: 1

      Yes, it's a big problem. The maximum transfer rate for a typical laptop hard disk is around 30MB/s on straight-line reads. Every seek costs somewhere from 5-10ms. If we assume it's 5ms and infinitely fast on linear reads, then a disk with 512byte blocks seeking after every block has a maximum transfer rate of 100KB/s. Seeking every other block brings it up to 200KB/s. Seeking every 10 blocks is still only around 1MB/s.

      --
      I am TheRaven on Soylent News
    9. Re:Untested performance... by vegiVamp · · Score: 0

      I'm far from hot on these things, but since there is (almost ?) no "spin-up" or -down, I imagine you could use an extremely agressive power policy.

      --
      What a depressingly stupid machine.
  4. Noise? Heat? by pipatron · · Score: 2, Interesting

    Dunno about the author of this article, but got an "SSD" (hello buzzword) to get rid of the noise, the heat, and the annoying spin-up delay. A compactflash card doesn't cost eleventy billion dollars either.

    --
    c++; /* this makes c bigger but returns the old value */
    1. Re:Noise? Heat? by NeutronCowboy · · Score: 1

      Not to mention shock-insensitivity and power consumption. Write speed to me is fairly irrelevant by now.

      --
      Those who can, do. Those who can't, sue.
    2. Re:Noise? Heat? by fm6 · · Score: 1

      If you want to spend all that money to eliminate spin-up delay, it's yours to spend. But the hard drive in my tablet makes almost no noise. And the heat generated by a hard drive motor is trivial; most of the heat in any electronic system comes from circuits, and an SSD actually has more of those. Though the main source of heat in your typical portable system is your CPU, which contains millions of transistors.

    3. Re:Noise? Heat? by pipatron · · Score: 1

      Oh, ok, thank you for the lesson! I guess the temperature drop from hothot to ambient was just imagination. The noise drop from some noise to absolutely zero noise must have been unnoticable as well.

      --
      c++; /* this makes c bigger but returns the old value */
    4. Re:Noise? Heat? by drinkypoo · · Score: 1

      Whenever I've eliminated fan and disk noise from a laptop I can hear the backlight inverter. I still think the biggest win is from power savings.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  5. Combination? by Lord+Pillage · · Score: 1

    Could a combination of these two technologies produce a more efficient HD. Let's say you used the HDD for writing data and then during idle time have the newly written data copied over to the SSD. Then one could read from the faster SSD. That way you would get the faster reading and writing speeds of each technology. I suppose that this however would be more expensive, but if the SSD were optimized for retrieval of data instead of storing, maybe this could be optimized further.

    --
    try { Signature mysig = new CleverAttempt(); } catch(NonCleverSignatureException e) { postanyway(); }
    1. Re:Combination? by tab_b · · Score: 1

      It seems a little bass-ackwards to have the mechanical device buffering for the solid-state one :) Maybe what you need is just more simply to have two separate devices in your laptop, a small SSD to hold your OS and apps, say a 32 GB Transcend for only $175 or so, and then a low-power, set to sleep ASAP traditional drive for your data, movies, or whatever else.

    2. Re:Combination? by alan_dershowitz · · Score: 1

      For files that aren't huge, the operating system write caching should already speed up this operation. Regarding what you asked about, that almost sounds like it could be a specialized modification of RAID-1, which would be cool.

    3. Re:Combination? by T-Bone-T · · Score: 2, Informative

      There are already drives that have platters and flash. They cache frequently used files in flash and bootup files when you shut down.

    4. Re:Combination? by insane_machine · · Score: 1

      Putting a traditional drive in conjunction with a SSD is pointless in a laptop. Just carry a 2.5" external HDD for your data and porn.

    5. Re:Combination? by Anonymous Coward · · Score: 0

      A combination yes, but not these technologies. What about combining SSD and high-speed cache of some sort. Why not have a smaller buffer that can be exploited for the save processes that are generally smaller than Gigs. Then you should be able to have the effects of saving even faster than mechanical...just don't turn off power before the cache has saved or make sure there is a battery installed that provides the minimum amount of time to off-load a full cache.

  6. Buzz by esocid · · Score: 1

    It's nice to know all that buzz is worth ignoring since I just bought a fancy new 750gig sata hdd. Even 16mb caches beat them solidly, I wonder how 8 and 32 would compare. It's worth noting they didn't mention seek times, although I'm not sure how that would transfer into ssd terms.

    --
    Absolute power corrupts absolutely. indymedia
    1. Re:Buzz by Kjella · · Score: 1

      It's nice to know all that buzz is worth ignoring since I just bought a fancy new 750gig sata hdd. Even 16mb caches beat them solidly, I wonder how 8 and 32 would compare. It's worth noting they didn't mention seek times, although I'm not sure how that would transfer into ssd terms.
      Reply to This In the places I've seen mentioning, it's on the order of nanoseconds. Anyway, all this shows is that you can pick the benchmarks you want to get the conclusion you want. Look at this from Anandtech. If you cherry pick your results, you can conclude with everything from HDDs being worse than SSDs to SSDs completley annihilating HDDs with a 7:1 advantage.

      The breakdown is pretty easy:
      Reading large, sequential media (photos, music, video): HDD
      Writing large, sequential media (capture, encoding, content creation): HDD
      OS/Application/Game loading (and other mostly read jobs): SSD

      It doesn't take a genius to understand that a SSD as system disk and HDD as media disk is the best deal. I just think the prices are still a little too extreme, but I'll be getting a small SSD with a few years. I'm not interested in the 128GB+ SSDs, I'm interested in a cheap... 8GB? SSD which should hold a decent enough install.
      --
      Live today, because you never know what tomorrow brings
  7. What about reliability? by maynard · · Score: 1

    Would an SSD take the hit of a drop better than spinning media? I betcha it would. Also, these are apples to oranges comparisons here - when was the last time you saw a MacBook Air equipped with a 3.5" 7200rpm Barracuda drive?

    IMO: I'm already recommending the purchase of SSDs in laptops for all of our top professionals where I work. And the reason is not performance, it is for reliability.

    1. Re:What about reliability? by ColdWetDog · · Score: 1

      Would an SSD take the hit of a drop better than spinning media? I betcha it would ... I'm already recommending the purchase of SSDs in laptops for all of our top professionals where I work. And the reason is not performance, it is for reliability.

      Maybe if your top professionals got some counseling, they wouldn't be tossing their laptops all over the place. Just who do you work for anyway? Microsoft?

      --
      Faster! Faster! Faster would be better!
    2. Re:What about reliability? by Anonymous Coward · · Score: 1, Insightful

      Well I hope your resume is up to date...

    3. Re:What about reliability? by maynard · · Score: 1

      I don't make who I work for public any longer.

    4. Re:What about reliability? by ColdWetDog · · Score: 1
      It's a joke, son. Laugh.

      Or not.

      --
      Faster! Faster! Faster would be better!
    5. Re:What about reliability? by maynard · · Score: 1

      Not.

    6. Re:What about reliability? by NekSnappa · · Score: 1

      No, American Tourister. In the testing department.

      --
      I want to shoot the messenger!
    7. Re:What about reliability? by piojo · · Score: 1

      Your annoyance on this topic just makes me more curious about where you work ;). Ah, well, I probably wouldn't reveal personal information of that sort, either.

      --
      A cat can't teach a dog to bark.
    8. Re:What about reliability? by maynard · · Score: 1

      I'm annoyed about the topic because some online assholes - many years back - took it upon themselves to contact me personally at work and threaten me with contacting my superiors over posts here and at another web site. I've not made my employer public since that time.

      Sorry I got pissed at you though, you had nothing to do with that. I'm just a little over-sensitive.

    9. Re:What about reliability? by piojo · · Score: 1

      It wasn't me you replied to; I was just chiming in (sorry for being ambiguous). As for putting personal details online, I agree that it's often wise not to--jerks/criminals aside, I don't want things I say online to come back to haunt me.

      --
      A cat can't teach a dog to bark.
  8. Not very good reasons... by MrKevvy · · Score: 4, Insightful

    Computerworld compared four disks, two popular solid state drives and two Seagate mechanical drives, for read/write performance, bootup speed, CPU utilization and other metrics.

    But of course not the metrics that really matter, which SSD's vastly excel at and make them worth the price for many people: MTBF, power consumption, ruggedness and noise level.

    --
    -- Insert witty one-liner here. --
    1. Re:Not very good reasons... by Mordok-DestroyerOfWo · · Score: 5, Insightful

      If I remember correctly the first LCD monitors were exorbitantly expensive and couldn't hold a candle to their CRT brothers. But since they saved so much space and energy, within a few years those problems vanished. I'd say it's still too early to close the books on SSDs.

      I know it's not a car analogy, I humbly beg the forgiveness of the /. community.

      --
      "Never let your sense of morals prevent you from doing what is right" - Salvor Hardin
    2. Re:Not very good reasons... by MightyYar · · Score: 1

      I know it's not a car analogy, I humbly beg the forgiveness of the /. community. SSDs are just heated mirrors in a fancy 2.5" form factor.
      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    3. Re:Not very good reasons... by Digi-John · · Score: 1

      LCD monitors still don't match up to a decent Trinitron. The only thing that comes close, in my opinion, is the massive old Samsung SyncMaster 240T that I've been using at work. It's 24" widescreen, does 1920x1200, and has a power brick that is actually pretty close to brick size. It's a tank. It would have been something like $5,000 back when it was new... and I salvaged two of them from the re-app pile.

      --
      Klingon programs don't timeshare, they battle for supremacy.
    4. Re:Not very good reasons... by Isao · · Score: 1
      ...MTBF, power consumption, ruggedness and noise level.

      Similar story over at StorageMojo and Robin draws a similar conclusion.

      MTBF - Infant failures about the same as discs, return rates higher
      Power - Flash already near the bottom of the power curve, drives appear to have room to drop
      Ruggedness - No moving parts a plus, perhaps countered by whole-block rewrites on write. Not enough data here
      Noise - Flash wins, no contest

      Bottom line? Not enough improvement to justify the cost, except in certain edge-conditions (like the eee PC).

    5. Re:Not very good reasons... by PIBM · · Score: 1

      I can't find a single CRT that beats up my 3007 WFP at 2560x1600, and I have much more space available on my desk than with the old 19" trinitron at 1940x1600!

    6. Re:Not very good reasons... by graphicsguy · · Score: 1

      Trinitron is no more (well, discontinued in USA and Canada in 2007).

    7. Re:Not very good reasons... by Tenebrousedge · · Score: 1
      Well, that depends on what exactly you need a monitor for. Generally the only really big issues has been contrast ratio (which on a CRT AFAIK is infinite) and color accuracy, which most LCD monitors don't even attempt to achieve. Distorted colors tend to be more eye-catching (and probably more eye-straining), and most consumers are more interested in something that "looks good" than something that displays colors accurately. That said, there are a number of really expensive LCD monitors from NEC that promise 100%+ Adobe RGB and/or NTSC that I drool over on a regular basis but have no real use for anymore, and I would be keenly interested in seeing how those stacked up against a top-of-the-line CRT.

      On a side note, I checked the specs on your monitor there, and I'm not seeing anything terribly impressive. Unless you can point to some actual objective measurement where this monitor (1st gen LCD?) surpasses all subsequent creations, I'm afraid I'm going to have to ignore your opinion.

      --
      Those who advocate genocide deserve every protection afforded by law, and none afforded by common human decency.
    8. Re:Not very good reasons... by Anonymous Coward · · Score: 0

      LCD monitors still don't match up to a decent Trinitron. The only thing that comes close, in my opinion, is the massive old Samsung SyncMaster 240T that I've been using at work. It's 24" widescreen, does 1920x1200, and has a power brick that is actually pretty close to brick size. It's a tank. It would have been something like $5,000 back when it was new... and I salvaged two of them from the re-app pile. I think you might be a bit biased:
      # Contrast Ratio: 450:1
      # Luminance: 230cd/m2
      Have you actively used any modern high end LCD's lately? Those monitors were great in their day, just like the Trinitrons, but honestly they dont touch the # of colors, max resolution, luminance, and contrast of modern day flat panels.
    9. Re:Not very good reasons... by The+Outlander · · Score: 1

      I think a quick check of LCD's is in order One of the best CRT's can offer 93.3% NTSC colours, My LCD (Samsung XL20 does 114%) Source NEC Displays - http://www.nec-display-solutions.com/c/g/uk/en/Contact/Home/cp/Internet/Subsidiaries/United_20Kingdom/Content/DynamicNavigationTeasers/Contact/Home/WideColourGammut.html

    10. Re:Not very good reasons... by turing_m · · Score: 1

      Perhaps more important than the 1-2 Watts you might be saving by switching from 2.5" HDD to SDD is the perceived speed increase in opening applications and booting. This means you can run a slower CPU for the same performance while saving much more power.

      --
      If I have seen further it is by stealing the Intellectual Property of giants.
    11. Re:Not very good reasons... by Deliveranc3 · · Score: 1

      >1ms second seek time across raid doesn't do anything for you?

      SSD + Raid, even with the mediocre performance we're seeing will be killer.

      SSD in the data centre is going to be interesting, data ining apps will evolve in entirely new directions.

  9. Power Consumption by Ironsides · · Score: 3, Insightful

    Too bad he didn't include power consumption. If I'm going to use an SSD for anytime soon, it will be in a laptop where power is my key concern. Performance is more of a desktop/high end issue right now.

    --
    Fly me to the moon Let me sing among those stars Let me see what spring is like On jupiter and mars
    1. Re:Power Consumption by NormalVisual · · Score: 2, Interesting

      In addition to power usage, some measure of how warm they get under load would be useful too.

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
    2. Re:Power Consumption by bromoseltzer · · Score: 1

      Power usage = Power dissipated in heat. It's virtually the same thing. Temperature rise is proportional to power dissipation divided by thermal conductivity to the outside world (your lap or room air).

      The RiData unit is specified at about 2.1 Watts, read or write. (Standby power might be much less, but they don't give a number.) The 200 GB Seagate drive is spec'd at 2.1 W during seek and under 1 W in idle/standby. So the power saving on the RiData active SSD is not much.

      --
      Fiat Lux.
    3. Re:Power Consumption by Humba · · Score: 1

      Power consumption is indeed better, but the hard disk accounts for only about 5% of the laptop power budget, so the changes don't significantly impact the run time. What is interesting (on the Lenovo x300 I've been using) is that the faster disk helps offset the slower, low-voltage processor. The low-voltage processor does help run time.

  10. Shocking Revelations! by capt.Hij · · Score: 1

    So if I read this right, if you purchase brand new, high priced technology it may not give you the same kind of bang for the buck as tried and true established technology. I... am... shocked....

  11. Performance is not the key to SSD by avdp · · Score: 2, Insightful

    IMHO, performance is not the critical factor regarding SSD. Power usage, and mostly no-moving-part (quiet and rugged) is why you want SSD in your laptop.

    But on the performance front, they compared with 7200RPM hard drives, last time I checked (admittedly a while ago) most laptop are outfitted with 5400RPM drives.

    1. Re:Performance is not the key to SSD by Sancho · · Score: 3, Insightful

      http://www.appleinsider.com/articles/08/02/07/macbook_air_hdd_and_ssd_battery_benchmarks.html indicates that the battery usage (at least compared to the HDD shipped with the Macbook Air) is negligible. No moving parts is nice, though manufacturers have addressed some of the ruggedness issues by including drop sensors. Actual, real world wear hasn't had a chance to surface yet--I'll definitely be curious to find out if SSDs live up to the speculation.

    2. Re:Performance is not the key to SSD by esocid · · Score: 1
      Most probably were, but the two they compared the to are laptop hdds. Since the comparison is talking about Macbook Air, I looked at the specs:

      Apple MacBook Air - 1.6GHz OS X 10.5.1 Leopard; Intel Core 2 Duo 1.6GHz; 2,048MB DDR2 SDRAM 667MHz; 144MB Intel GMA X3100; 80GB Samsung 4,200rpm
      The stock hdd is 4200rpm so even that 5400 figure you had was over the stock drive speed. So they should have compared those two options as well as what they did to get a good idea. As well as including drives with 8mb and 32mb caches.
      --
      Absolute power corrupts absolutely. indymedia
    3. Re:Performance is not the key to SSD by avdp · · Score: 1

      And since this is a 4200RPM drive, it seems it's impossible to get a good picture of all the metrics side by side.

      Another concern, which I forgot from my original post is heat. And I am sure heat is key concern with a laptop like the Mac Air

    4. Re:Performance is not the key to SSD by Anonymous Coward · · Score: 0

      mod parent up. the machines that are using SSD (Apple, Dell, Lenovo, etc) are in the lightweight category and they currently don't make drives faster than 5400. I thought most were 4800 actually. which is painfully slow.

    5. Re:Performance is not the key to SSD by code4fun · · Score: 1

      To be fair though, Samsung just came out with SSD that can do 100MB/s. I'm guessing the one that comes with the Air does not. I'd say wait a while for SSD to mature and for the price to come down. I agree, in general, what the author is saying. http://www.tgdaily.com/content/view/36084/118/

    6. Re:Performance is not the key to SSD by Anonymous Coward · · Score: 0

      The AllThingsD test mentioned on that page was pretty stupid -- set up to use power on everything but the HD. The Anandtech test doesn't test the SSD. Nothing to see here, move along, move along.

  12. Why a "drive"? by Ossifer · · Score: 3, Interesting

    Am I the only one questioning why these devices are implemented using a mechanical drive interface? Maybe it's a negligible cost, but to me it would seem that a memory bus optimized for flash memory would be a better way to go, than trying to piggy-back a mechanical drive's bus. How much faster could these be if their existence was planned into, say Intel's chipsets?

    1. Re:Why a "drive"? by Wesley+Felter · · Score: 1

      We'll find out soon, since Intel is adding a flash controller to its chipsets.

    2. Re:Why a "drive"? by Alioth · · Score: 3, Informative

      Well, the IDE bus isn't mechanically oriented anyway - we don't actually use cylinders, heads and sectors (and haven't for years), we use block addressing and the drive electronics has figured out how to move the mechanics. Block addressing isn't all that far off from addressing an individual byte in memory anyway - except you're addressing a whole block rather than a single byte (and for mass storage, whether it's mechanical or flash, you're going to want to do it that way so you don't have an absurdly wide address bus). Parallel ATA uses a 16 bit wide data bus.

    3. Re:Why a "drive"? by rubeng · · Score: 1

      Yeah, but think how much simpler it would be if the flash memory was directly mapped into the processor's address space, no IDE/SATA/SAS drivers, no logical blocks, just a memory range 0xwhatever to 0xsomething else that was non-volatile. You'd still want a filesystem to manage that memory though.

    4. Re:Why a "drive"? by Ossifer · · Score: 2, Interesting

      Thanks for the information and insight, but I wonder, why wouldn't we want a (maybe not "absurdly") wide address bus? A 16-bit wide bus seems a bit underscaled, considering core memory buses are 128 bit, and with block addressing we're obviously reading/writing much more than that. The core memory bus is already 16 times bigger than the smallest addressable unit. Granted, with say a 512-byte block, I'm not suggesting a 64k bit wide bus (16 * 512 * 8), but it would seem that 16 bit is simply not a good choice...

    5. Re:Why a "drive"? by Jeff+DeMaagd · · Score: 1

      SSDs are not even close to maxing out the drive interface anyway, so is it really even a relevant consideration?

    6. Re:Why a "drive"? by HonIsCool · · Score: 1

      These days flashrom (NAND) are inherently addressed in blocks.

      --
      "Give me six lines of C++ code written by the most competent programmer, and I will find enough in there to hang him."
    7. Re:Why a "drive"? by HonIsCool · · Score: 1

      The 128-bit address bus, for when you really need access to that udabyte(*) storage device...




      (*) 1 udabyte = 1000000000000000000000000 terabytes...

      --
      "Give me six lines of C++ code written by the most competent programmer, and I will find enough in there to hang him."
    8. Re:Why a "drive"? by Ossifer · · Score: 1

      Well, not for addressability, but for parallelism...

    9. Re:Why a "drive"? by Alioth · · Score: 1

      The data bus for parallel ATA is 16 bits wide. Block addresses are 48 bits wide (you'll see lots of references to 48 bit LBA if you poke through stuff that deals with ATA).

    10. Re:Why a "drive"? by Anonymous Coward · · Score: 0

      SATA, SAS are serial. One direction differential pair is the future. Some other technologies that use single direction differential pair:
      USB
      ethernet

      So the "width" of the address doesn't really correspond to anything physical.

      The larger issue is the huge institutionalized momentum behind current storage standards. Lets say you are Joe SSD maker, and you want to get a product to market. You have the following options:
      1- get every O/S and BIOS and motherboard and HBA out there to have a special new SSD protocol/interface (or only be compatible with a tiny subset of them)

      2- just make your new device emulate the old device, with maybe a few optional extensions to current standards and work with the entire existing eco-system

      Coordination between O/S writers, controller chipset makers, and SSD manufacturers takes time. O/S changes will come first since they don't have per-unit costs to shipping new functionality.

    11. Re:Why a "drive"? by Ossifer · · Score: 1

      2- just make your new device emulate the old device, with maybe a few optional extensions to current standards and work with the entire existing eco-system

      Right, so I guess my original question is, is this (bridging) solution holding us back in some way (in terms of performance)?

    12. Re:Why a "drive"? by Tord · · Score: 1

      One reason to not have more than a 16-bit wide bus is that you don't want too thick cables going to the drive. For every bit you need one separate, isolated connection in the cable.

      Thick cables are clumsy, more expensive to make and break more easily.

      Of course, you could have a wider interface and multiplex the signal in the cable, but that wouldn't give any performance gains.

    13. Re:Why a "drive"? by PipsqueakOnAP133 · · Score: 1

      There's nothing in ATA that is really specific to mechanical drives since LBA basically addresses it as an array anyways.

      Additionally, typical NAND chips are 20MB/sec. While NAND is solid state, it compares unfavorably to, say DRAM.
      There are a few chips on the market that go as high as 50MB/sec, but they're rare. And even then, ATA66 would still be enough to connect to it.

    14. Re:Why a "drive"? by Ossifer · · Score: 1

      But aren't we addressing multiple flash chips in parallel? What about local DRAM caching? Mechanical drives have this, as well as multiple platters/heads...

    15. Re:Why a "drive"? by PipsqueakOnAP133 · · Score: 1

      There is actually no guarentee that they're all being accessed in parallel. The reason for this is because the block size for each chip is larger than the normal LBA block size. Which means that either you cache this for a while in DRAM (less likely), or you write back a merged block (more likely).

      Normally, when you access a memory chip, you typically have all the lines(wires) tied together except for a chip select, which tells the chip, you're the one being accessed. This is to reduce the number of lines coming from a controller because IO lines are expensive to make. Hence why USB drives that are dual-channel are much more expensive and rare.

      So, an example would be, for single channel it takes 50 lines total to connect to a single NAND chip.
      51 lines to connect to 2 NAND chips.
      52 lines to connect to 3 NAND chips.

      What you're asking for, simultanious access to all NAND chips would be....
      50 lines to connect to a single NAND chip.
      100 lines to connect to 2 NAND chips.
      150 lines to connect to 3 NAND chips. Pretty crazy huh?

      Adding in the lines to support DRAM would increase the cost even more.

      Aside from increasing chip costs, adding in lines would make the board harder to layout to prevent crosstalk and corruption. It's the same reason why it's rare to find motherboards with more than 4 DIMM slots. It's hard to layout that many lines.

      Overall, it'd be nice if we could cache and package each block in DRAM and write/read them from NAND in parallel. But it increases development costs significantly. Probably by whole number factors.

    16. Re:Why a "drive"? by Ossifer · · Score: 1

      Ok, I get it, but I am assuming your "50" is a guess. Even if it is exactly correct for one chip, I assume it is likely that simultaneous access to multiple chips would still be feasible without n×50 total lines. For example, I would assume it would be acceptable to tie together all +5V lines, GRND, etc. Taken to the other extreme, one would inherently need only n×w + 50 - w lines, where w is the data bus width. Given n = 3, w = 8, total lines is only 66...

      Of course there are probably additional lines beyond the data bus that can't be shared, but in reality the number is certainly somewhere in between w and "50"...

    17. Re:Why a "drive"? by PipsqueakOnAP133 · · Score: 1

      You're right, I threw 50 out there as a guess since I didn't have a datasheet at hand and it had been a while since I read any datasheets regarding memory.

      Now that I looked up a datasheet for the Samsung K9LAG08U0M (the NAND chip in the 8gb iPod and iPhone), and Toshiba's NAND flash interface design guide (kinda old though), I found some additional interesting things.

      1) Assuming we're using NAND flash, many large NAND Flash chips are actually 4GB NAND Flash chips stacked internally, with multiple chip enable lines. This means that we're kinda forced into not doing simultaneous access for high density chips past 4GB.
      The 8GB one is 2 4GB chips stacked in the same package. The 16GB one is 4 chips stacked.

      2) There appears to be a standard interface for NAND Flash across manufacturers where 528 bytes are written out at a time in small block mode and 2112 in large block mode.
      And it has a small block and large block mode. It seems to max out at 4GB.

      3) To access a single 4GB chip, you definetely need unique IO0-7 and CE. 9 lines.
      You may be able to share CLE, ALE, Ready, WE, RE if you're always writing to blocks at the same time. This isn't true when a block fails writing. So you shouldn't share these either. Makes for a total of 14 unshared lines.
      Obviously shared lines are Power, Ground, Write Protect.

      So, you're right, for a bus to NAND connection, it wouldn't be too bad to have a controller that provides 14*N lines, where N is the number of chips to access simultaneously. The board layout difficulty would still grow significantly as you add more chips though.

      Adding a DRAM cache to help reordering, buffering, and deferring block checks would also be painful. Micron says for a 64MB SDRAM chip, you'll need 12 address lines, up to 16 Data lines, and about 8 more control lines. Pretty darn ugly. That's probably what made me incorrectly assume 50 lines.

  13. Stupid Test by phantomcircuit · · Score: 4, Informative

    They only tested burst speeds, there was no random access testing.

    SSD works best when accessing files randomly.

    1. Re:Stupid Test by somersault · · Score: 1

      [Channel-surfing]
      Rex: Go back, go back, you missed it.
      Hamm: Too late, I'm already on the 40's, gotta go around the horn, it's faster.
      --
      which is totally what she said
    2. Re:Stupid Test by Sleepy · · Score: 2, Insightful

      +1

      This is like a hybrid vehicle vs normal gas shootout, with each vehicle towing something. It's irrelevant.

      He boiled down all the variables and performance profiles into just one - the one that favors traditional drives. There is NO WAY this should have been published as-is.

      I can't attribute this to malice, but basically Bill O'Brien of Computerworld DOESN'T KNOW WHAT HE'S DOING, and neither does his editor for letting this slide. This was probably a case of a traditional drive maker whispering in his ear that this would make a GREAT expose, and not knowing any better he walked right into it.

      Besides power savings, and heat, these drives kill spinning discs on certain applications such as a read-mostly database server or file server, or any server that handles queues of small-files where a normal drive would have a read head all over the place.

      Unbelievable. This is why I avoid magazine reviews and focus on (usually) better sources like Anandtech, Toms, etc. ComputerWorld is like ComputerShopper...

    3. Re:Stupid Test by Anonymous Coward · · Score: 0

      Unbelievable. This is why I avoid magazine reviews and focus on (usually) better sources like Anandtech, Toms, etc. ComputerWorld is like ComputerShopper... I assumed that 'Toms' meant TomsHardwareGuide, have you ever noticed the slew of advertising. Not surprisingly all their advertisers always, with few exceptions, get the best reviews.
  14. I've seen this before. by jskline · · Score: 2, Insightful

    You really have to look deep into the advertising sometimes. Only a trained person willing to do the math on these would be able to see the differences. Clearly, these devices have a legitimate purpose and place, but at this point in time, its not in the client computer. The speeds need to come up to be really practical.

    Now a good purpose for these might be in desktop bound short-stack storage arrays instead of that large tera-byte drive array. They're just quick enough for data retention backups off of the mechanical drives in the client PC.

    Another use is small-scale server apps that usually are bound into hardware in some form of internet controllable appliance. Speed isn't really a major factor here for this and these would potentially work well.

    Just my opinion. Subject to change.

    --
    All content in this message is copyright (c) 2008. All rights reserved. RIAA is prohibited here.
  15. SSDs are ideal for servers by ncw · · Score: 4, Insightful

    As any sysadmin knows, on a busy server what creams the disk isn't Megabytes per second, it is IO transactions per second.

    According to the article the Crucial SSD has an access time of 0.4 ms which equates to 2500 IOs/s as compared to the Barracuda HDD with 13.4 ms access time which equates to a mere 75 IOs/s.

    So for servers SSDs are 33 times better!

    Bring them on ;-)

    --
    Every man for himself, all in favour say "I"
    1. Re:SSDs are ideal for servers by Bill,+Shooter+of+Bul · · Score: 1

      Exactly. I guess the point of this article was to examine weather or not it made sense in the case of a laptop,as many are now starting to offer one as an option. But it would have been nice to point out the real awesome potential they have for servers.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    2. Re:SSDs are ideal for servers by Uncle+Focker · · Score: 1

      Have fun changing out the drives every year as you've surpassed the maximum number of writes.

    3. Re:SSDs are ideal for servers by Anonymous Coward · · Score: 0

      I wonder what the performance in a RAID setup would be like? It should be awesome.

    4. Re:SSDs are ideal for servers by mapsjanhere · · Score: 1

      Well, they would be if they had unlimited read-write cycles. But flash is rather more limited in that regard, some estimates are as low as 100,000 cycles.
      If your 2500 IOs/s hit the same sector, your server SSD is fried in 7 min. SSD are distinctively NOT server suitable if you have a lot of write cycles (probably less of an issue if it's just answering read requests).

      --
      I'm aging rapidly, I bought a new game and had no idea if my machine was good for it.
    5. Re:SSDs are ideal for servers by vux984 · · Score: 1

      If your 2500 IOs/s hit the same sector, your server SSD is fried in 7 min.

      One would think that would actually be an ideal scenario. Your cache hits would be through the roof. Even if it wrote the sector back to the flash drive once every 2 seconds, that would be 5000 IO's worth of updates in one write op.

      Factor in drive wear leveling (so that it moves the data sector around on the empty space on the physical disk rather than in the same physical place each time), and the disk would probably last nearly forever.

    6. Re:SSDs are ideal for servers by hardburn · · Score: 2, Interesting

      If your filesystem is designed to distribute the writes properly, the failure time is comparable to the MBF of hard drives.

      Though personally, I think the way to go on servers is to use 64GB of RAM and put most of it as a RAM disk. Depending on your application, you can either have a shell script copy the data back to a hard drive for persistent data, or use that kernel driver to mirror the data to a hard drive. Software RAID 1 would work, too.

      --
      Not a typewriter
    7. Re:SSDs are ideal for servers by LWATCDR · · Score: 1

      That would really depend on the server.
      A good example where an SSD might be a good solution is one of the database servers at my office.
      A record gets created and then updated maybe twice. It then my get read a few hundred thousand times.
      So yes for some servers it might be a really good thing. Lots of databases are very very read heavy and write light.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    8. Re:SSDs are ideal for servers by somersault · · Score: 1

      But in the case for read requests it is better. Obviously HDs are currently better for some applications, but likewise SSDs are also better for some applications. Yet again, people seem to be herding each other into camps and throwing rocks at each other rather than just learning the merits of each other's viewpoints and using the best tool for the job.

      --
      which is totally what she said
    9. Re:SSDs are ideal for servers by pancrace · · Score: 1

      Real-world results are even more dramatic, we run about 50x better than a U320 15k drive with a read-only database.

      But the use of flash drives for servers is still quite limited. I wouldn't use it for anything with large amounts of sequential IO, but only for lots of random IO in very small chunks (4k or less). Even a slow HD beats the flash drive for reading many files over 512K and a HD clobbers flash on any kind of writing.

      IME, large databases with very few UPDATES/INSERTS and very sparse file systems are pretty much all that run well.

      - p

      --
      I don't have a .sig
    10. Re:SSDs are ideal for servers by AlexCV · · Score: 2, Informative

      Not only does wear leveling on very large (> 100 GB) completely moot the point *even* with 100000 cycle life, but modern high-capacity flash has cycle life in the millions of cycles, they have extra capacity set aside to deal with cell failures, they have error correction/detection, they have wear leveling. We're a long way off using FAT16 on straight 128 megabits flash chips...

      I don't know why everyone keeps repeating flash "problems" from the mid/late 90s. We're in 2008, flash has been widely used in huge quantities for well over a decade with thousands of engineers applying well understood solutions to the problems.

    11. Re:SSDs are ideal for servers by mapsjanhere · · Score: 1

      I'm aware that you can get around this issue, I was just trying to point out that the raw "possible IO" number is not all it's cracked up to be.
      Similar for using it as a specialty device for read heavy applications; it was the general "ideal server device" that I had a problem with.
      When I first read about SSD it sounded like the second coming of sliced bread, it was the "devil in the detail" that soured me, especially the write limitations that seem to be a physical limitation, not something you can engineer away.

      --
      I'm aging rapidly, I bought a new game and had no idea if my machine was good for it.
    12. Re:SSDs are ideal for servers by cameldrv · · Score: 1

      This is only true for reads. For random writes, Flash based SSDs are much slower than hard drives, and that's why they didn't do well in this test. The problems are surmountable, but the first step is for tests like this to be widely publicized, so that users start looking more closely at the specs of drives.

    13. Re:SSDs are ideal for servers by AlexCV · · Score: 2, Insightful

      FUD!

      A modern SSD is able to handle write intensive database application with reliability on par with HDDs. The SSD logic spreads the writes around the disk to prevent premature wear so a record updated a million times might well never be written twice over any given flash cells. And even at 512 bytes each, there's 195 millions of them on a 100GB SSD. Each of which has about a 1 million cycle life and there's normally spare cells to handle failures. I'll take that over a SCSI disk.

    14. Re:SSDs are ideal for servers by Uncle+Focker · · Score: 1

      If your filesystem is designed to distribute the writes properly, the failure time is comparable to the MBF of hard drives. Sure if we were talking about normal desktop usage. He was implying that he would be trying to do thousands of IO operations per second on these SSDs which is going to wear out the drive much much faster.
    15. Re:SSDs are ideal for servers by Yvan256 · · Score: 1

      Is there any way to know if a certain device has built-in wear leveling capabilities?

      More specifically, I'm talking about CompactFlash cards, since they can be used as an IDE drive with a simple 10$ adapter.

    16. Re:SSDs are ideal for servers by vux984 · · Score: 1
      I think its already been engineered around. Something -else- in the system will generally break down long before the flash media is toast.

      Flash chips with 300,000 write cycles are common, and currently the best flash chips are rated at 1,000,000 write cycles per block (with 8,000 blocks per chip). Now, just because a flash chip has a given write cycle rating, it doesn't mean that the chip will self-destruct as soon as that threshold is reached. It means that a flash chip with a 1 million Erase/Write endurance threshold limit will have only 0.02 percent of the sample population turn into a bad block when the write threshold is reached for that block.

      The better flash solid state flash drive manufacturers have two ways to increase the longevity of the drives: First, a "balancing" algorithm is used. This monitors how many times each disk block has been written. This will greatly extend the life of the drive. The better manufacturers have "wear-leveling" algorithms that balance the data intelligently, avoiding both exacerbating the wearing of the blocks and "thrashing" of the disk: When a given block has been written above a certain percentage threshold, the solid state flash drive will (in the background, avoiding performance decreases) swap the data in that block with the data in a block that has exhibited a "read-only-like" characteristic.

      Second, should bad blocks occur, they are mapped out as they would be on a rotating disk. With usage patterns of writing gigabytes per day, each flash-based solid state flash drive should last hundreds of years, depending on capacity.

      If it has a DRAM cache, it'll last even longer.


      http://www.bitmicro.com/press_resources_flash_ssd.php

    17. Re:SSDs are ideal for servers by MushMouth · · Score: 1

      Do you have ANY idea what you are talking about?

      with all modern SSD's there is no reason to use some special file system. The drive itself writes to different physical locations on every write, and thus have a lifetime measured in 10-100 years before it wears out (even if you overwrite the same file constantly). As for IOPS usually those are about reads, which don't wear out a solid state drive at all, although they DO wear out mechanical drives. If make some complex sql query, or bin search files, in real world situations the solid state drive is orders of magnitude faster than a mechanic drive.

    18. Re:SSDs are ideal for servers by Uncle+Focker · · Score: 1

      Do you have ANY idea what you are talking about? Yes. If, as the OP was talking about, you are doing thousands of IO operations per second on an SSD you aren't going to get the generous long life that is quoted when talking about "normal" desktop usage.

      with all modern SSD's there is no reason to use some special file system. The drive itself writes to different physical locations on every write, and thus have a lifetime measured in 10-100 years before it wears out (even if you overwrite the same file constantly). Please quote me your source on the 100 years claim cause that's utterly ridiculous. No manufacturer even claims such nonsense. Secondly, the figure of 10+ years is again for normal desktop usage. We were talking about a server doing 1000s of IO operations per second. That's many magnitudes higher than what you'd see from a desktop user.

      As for IOPS usually those are about reads, which don't wear out a solid state drive at all, although they DO wear out mechanical drives. If make some complex sql query, or bin search files, in real world situations the solid state drive is orders of magnitude faster than a mechanic drive. Sure in certain situations the IO operations may be predominiately reads and for such cases an SSD may be beneficial. But there are plenty of servers that are doing tons of writes and as such an SSD is going to wear out very, very fast.
    19. Re:SSDs are ideal for servers by owlstead · · Score: 1

      As I understood, this depends on the amount of information stored per cell. Those cheaper memory modules are almost as fast as those that store a single bit per cell, but the disadvantage is more wear and tear (100k and less). Obviously, with wear leveling this is a bit of a moot point, but wear leveling slows down the process quite a bit.

      Obviously if you have a web-server with many reads and few writes all this matters very little. If you have a web server with many reads and quite a few drive: use SSD *and* a drive. I mean, it's not an exclusive OR isn't it? That's only the case when the data that is written many times is also the stuff that is read many times.

    20. Re:SSDs are ideal for servers by LWATCDR · · Score: 1

      But last time I checked SSD's write performance was pretty slow. Thing do change so that might be one. However for a mostly read database I can see how it would be ideal.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    21. Re:SSDs are ideal for servers by xZgf6xHx2uhoAj9D · · Score: 1

      A typical source is something like this. This is not looking at typical use: it's looking at writing to the drive constantly. In the worst case scenario, the drive would last 51 years. That article is out of date too. Flash drives could potentially last hundreds of years in the worst case these days.

      This is not to say that modern flash drives last hundreds of years, just that the number of rewrites is not the limiting factor. It doesn't matter how little free space there is on the drive, what access patterns you use, etc. Take a modern flash drive with no free blocks and write and rewrite to it non stop. It should last at least a few decades before the number of rewrites starts to become an issue.

    22. Re:SSDs are ideal for servers by TheRaven64 · · Score: 1

      I did the maths on flash drive lifespans a few /. articles ago. I took the total amount of data written to (any) disk in my laptop (my main machine - I haven't used a desktop for years) since the last reboot and used this to give a bytes-written-per-day value. I then assumed perfect wear levelling. With the quoted minimum number of rewrites for a modern Flash drive, one would last a shade over 900 years with my typical usage pattern. Even if wear levelling sucks and I only get 10% of that, I'd be ecstatic to have a drive that lasted 90 years. I don't think I have any hard disks more than 10 years old still in use - I have a stack of older ones that probably still work, but capacities have gone up so much since then that it doesn't make sense to keep them in use.

      --
      I am TheRaven on Soylent News
    23. Re:SSDs are ideal for servers by Anonymous Coward · · Score: 0

      I wonder what the performance in a RAID setup would be like? It should be awesome. Is this supposed to be the new "Imagine a Beowulf cluster of ..."?
    24. Re:SSDs are ideal for servers by Anonymous Coward · · Score: 0

      Try again: http://www.storagesearch.com/ssdmyths-endurance.html

  16. Well by Anonymous Coward · · Score: 0

    Reliability - http://gizmodo.com/369294/20-percent-of-ssd-notebooks-failingNope
    Speed - Nope

    Tell me again what the whole point was

    1. Re:Well by tab_b · · Score: 1

      An update on that Gizmodo page on reliability says Dell refutes those numbers pointing here.

  17. What about the power usage? by wiredog · · Score: 1

    That's the (potentially)biggest benefit of using SSDs over HDDs. No moving parts==less power used==longer battery life.

    1. Re:What about the power usage? by Overzeetop · · Score: 2, Informative

      That's true, but is almost a technicality with today's processors and video cards. With anything but the slowest ultra-portables, having a hd running just doesn't suck up much juice. A Seagate Momentus (5400rpm) takes between 1.9 and 2.3W when reading/writing/seeking, and only 0.8 watts when idle (not standby - that's .2W). Given a typical laptops with between 50 and 80 Wh batteries and a 2 to 3 hour charge life, you're HD comprises about 3% of the average draw at idle, and about 7-8% at full tilt - for those of you running active SQL servers on your lappies. If I give you 30% at non-idle, it's about 4%. That's more power than with a SSD at 0.2W, but it's really only about 4 to 6 minutes of extra time on a charge.

      --
      Is it just my observation, or are there way too many stupid people in the world?
    2. Re:What about the power usage? by Nexus7 · · Score: 1

      While true, consider also the case where I'm using the browsing the web... a lot of small files keep getting written to the disk, as soon as I finish reading one web page and go to the next. So the HDD keeps spinning up. So I increase the idle timeout. Now the disk just keeps spinning, and the palm-rest above the disk gets hot, decreasing the disk's lifetime. For some reason, even putting Firefox's cache into /dev/shm doesn't seem to help, disk spins up frequently. Things like ndiswrapper like to write to disk. This is why I'm considering an SSD. I don't think I'm going to take much of a performance hit compared to a 4200 rpm HDD.

    3. Re:What about the power usage? by Sentry21 · · Score: 1

      Given a typical laptops with between 50 and 80 Wh batteries and a 2 to 3 hour charge life, you're HD comprises about 3% of the average draw at idle, and about 7-8% at full tilt - for those of you running active SQL servers on your lappies. The SQL server I run on my laptop uses the query cache extensively, and thus makes considerable power consumption gains during high-load scenarios, you insensitive clod!
  18. I live on a boat by olele · · Score: 1

    that bounces a lot. and includes things like salt and generally high moisture in the air. I think anyone that uses their pc - whatever form factor - anywhere that's not sitting on a desk in a climate controlled environment might do well to take these results with a grain of salt *sorry*

  19. But what about the Noise level by dawnsnow · · Score: 1

    I've been suffering too long time from the hard drive noise. If the price is reasonable I want SSD to have quiet environment.

  20. it's all about the battery by Khopesh · · Score: 1

    SSD's performance boost is in battery life due to its lower power consumption from zero moving parts. Flash-based storage has always had a problem with writing; don't forget about the fact that it can only be written to ~1000 times.

    Furthermore, SSD is just temporary relief for batteries; I envision a laptop with both SSD and HDD that almost never writes to the SSD; on Windows, C:\WINDOWS and C:\Program Files would live in SSD while C:\Documents & Settings would live on HDD and C:\WINDOWS\Temp (or wherever that part lives nowadays) would be on ramdisk. On FOSS systems, /usr would be SSD while /home and /var would be HDD and /tmp and /var/tmp would be in shared memory (like /dev/shm).

    The real future is in racetrack memory and the like, which drastically improves speed in both directions, removes the 1000-writes issue, AND further boosts SSD's impressive battery life. However, we've got ten years before it hits the market, so we have SSD until then.

    --
    Use my userscript to add story images to Slashdot. There's no going back.
    1. Re:it's all about the battery by Alioth · · Score: 1

      That's not correct: even NOR flash (what you use for ROM, rather than mass storage) has been rated at 10,000 erase/write cycles for years - per sector (rather than the whole device). The typical flash mass storage is up to 100K erase/writes.

      Swap is the main concern here - the solution is to give the machine enough RAM that you can turn swap off.

    2. Re:it's all about the battery by Uncle+Focker · · Score: 1

      Flash-based storage has always had a problem with writing; don't forget about the fact that it can only be written to ~1000 times. You're a few orders of magnitude off. It's around 400-500 thousand reads for average flash drives. The more expensive, high performance stuff can max out at a few million writes.
    3. Re:it's all about the battery by KokorHekkus · · Score: 1

      I don't think there's any reason to believe that even swap would become an issue unless the drive has an extremely bad wearlevelling system. Why shouldn't any decent wearlevelling keep track of block use and swap heavily used blocks with those that have a read-only characteristic. With a wanted lifespan of 10 years the number of writes per year you'll get should be 10000 * number of blocks on the drive (using the conservative 100 000 write cycle limit).

      With a 64 gigabyte drive with a block size of 256 kilobytes (which sounds on the high side to me, sizes are usually from 16 kilobytes to 256 kilobytes from what I've read) you get 80 of those block writes per second, 24 hours a day, 365 days a year for 10 years before you start crossing the write limit. Make a drive with 128 kilobyte block size and you get the double etc.

    4. Re:it's all about the battery by Anonymous Coward · · Score: 0

      I'm pretty sure I've read an in-depth article about SSDs that said that the theoretical life of a SSD (SLC probably) was about 200 years. IF you wrote 100GiB/day. Might be wrong though.

  21. Not surprising or bad to me. by alan_dershowitz · · Score: 2, Informative

    Two things: first, booting is ideally going to be largely sequential reads because OS X caches files used in the boot process in order to speed up the boot by removing random access. SSD's have an advantage over hard drives in random reads because there's comparatively no seek time. So I wouldn't expect to see a huge advantage. Secondly, I'm not going to be using my macbook air's tiny SSD drive for analog video capture or something anyway, so high write speed is really not that relevant to me. On the other hand the thing is supposed to be light and use little battery, so SSD seems like it wins for the reasons it was used. Also, the tests bear out a higher average read speed, which is also what I would have expected. I don't see anything surprising here.

  22. Anyone? by ShiNoKaze · · Score: 1

    Anyone ever hear what happened to the second generation i-Ram from gigabyte? There was mad intel on the first and then it all just went away... I want the 8Gig, SATA 2. It just never came out.

    1. Re:Anyone? by danbert8 · · Score: 1

      Seriously, at current DDR2 prices, I could easily have a ludicrously fast hard drive big enough to store my OS for under 150 bucks.

      --
      Yes it's an anecdote! Were you expecting original research in a Slashdot comment?
    2. Re:Anyone? by 0111+1110 · · Score: 1

      They gave up on it. They just didn't have the expertise for making a real memory controller. At least that's what they said. These days 8 gigs of DDR2 would only cost around $80. A PCI-X 2.0 card or SATA 2 drive interfaced device with the slots and memory controller could probably sell for about a hundred. So we are talking under $200 for a battery backed 8 GB solid state drive that would be about as fast as the system RAM. Do incremental backups to the real hard drive in the background when there are free resources and have redundant rechargeable batteries as well as some source of power to keep them charged from the PSU even when the machine is "off" and you have a practical SSD without any of the disadvantages that make flash based SSDs only really useful for applications where durability/shock is a major factor or with size issues as in cameras or MP3 players or the Macbook Air.

      --
      Quite an experience to live in fear, isn't it? That's what it is to be a slave.
  23. What about battery life? by dpbsmith · · Score: 1

    I would have thought that in a laptop, solid state drives would have a noticeable advantage in terms of power consumption leading to increased battery life.

    Admittedly the article described itself as a performance showdown, but I'm disappointed that the reviewer made no attempt to compare power consumption and battery life.

    If nothing else, I would have thought a solid state drive would eliminate that annoying pause when a hard drive awakes from sleep and spins up, and that this would feel like a worthwhile "performance" improvement--though whether it's worth the cost is another question.

    1. Re:What about battery life? by CastrTroy · · Score: 1

      However, the flash drives are only 32 GB. How small and how low power could you make a drive that only needed to be 32 GB. You could probably go for a much smaller form factor. Which would mean smaller platters, which would take less energy to spin. It would also mean that the read/write heads wouldn't have to move as far to reach the data. Comparing a 32 GB SSD to a 3.5 inch, 250 GB HDD is not a very good comparison.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    2. Re:What about battery life? by Champ · · Score: 1

      I see your point, which is probably theoretically true to some extent, but have you actually TRIED a microdrive? They're terrible! Slow to spin up, slow to seek, slow to transfer. Less energy than regular drives, sure, but quite a bit more than flash.

      I have an 8 GB MicroSDHC card that's the size of my fingernail and about as thick. Four of those would be less than 0.5 cm^3. When you have a fast mechanical drive in the same form factor, let's talk.

    3. Re:What about battery life? by somersault · · Score: 1

      From a quick googling, SSDs seem to use about 1/4 of the power of HDDs (1 watt compared to about 4 watts), but when you put that alongside the screen (~4 watts), speakers (maybe 20 watts in a laptop? Not that you'd always have them up that loud :P ), wifi (~1 watt idle, up to 4 watts while in use) and such, I'd think that you aren't gaining much. It is a step in the right direction of course..

      http://www.codinghorror.com/blog/archives/000562.html is the link I used for a few of those figures

      --
      which is totally what she said
  24. Seek Times Make the Difference by pancrace · · Score: 5, Interesting

    We installed one of these for processing millions of small, read-only database transactions. The database only gets written once a day, but is too big for efficient cacheing. Even with a U320 15k drive we were still suffering, only being able to run about 700/min. With a flash drive, we're running over 25,000/min, peaking at 50,000/min. But the weekly copy of the database takes about 20 minutes, vs the 3 or 4 minutes it used to take.

    - p

    --
    I don't have a .sig
    1. Re:Seek Times Make the Difference by Anonymous Coward · · Score: 1, Informative

      CCP the company behind EVE online was one of the first major companies to install RAMSAN disks for the EVE database (a HUGE database, with a crazy amount of transactions per second).

      It improved certain aspects of the game 100x. It was an impressive improvement, even considering the money spent to do it.

  25. He forgot the two crucial tests.... by Anonymous Coward · · Score: 0

    A not-very-interesting comparison of read/write performance only. He should have run the two crucial tests that caused me to move to a solid state disk (made it myself out of an adapter and a high speed/large capacity CF card) for my traveling laptop. That would be the laptop that I throw in my carry-on and occasionally drop.

    First, compare and contrast laptop battery life while continuously reading and writing disk files; second, compare and contrast hardware reliability while holding the laptop in both hands and shaking it as vigorously as possible while reading and writing disk files.

    1. Re:He forgot the two crucial tests.... by somersault · · Score: 1

      compare and contrast hardware reliability while holding the laptop in both hands and shaking it as vigorously as possible while reading and writing disk files. Is that meant to simulate yourself having a close encounter with the opposite sex while the laptop is in your backpack downloading torrents, or what?
      --
      which is totally what she said
  26. Definitely not enough data by DrYak · · Score: 1

    ...And the survivability of mechanical drives in the ultra-portable form factor (more likely to be droped or tossed, more concentrated heat problems, etc.)

    Although some data from the Palm LifeDrive (featuring a mecanical Microdrive CF module) could answer the drop-survivability in small form factor.

    So, in short, they managed to produce only 1 single data i.e. bulk speed (well, not exactly. They also mentioned random access from a synthetic test, but no actual real-world application) when users would need about a dozen of others.
    Specially in the long term range (wearout of SSD vs. damage of HDD).

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:Definitely not enough data by mrchaotica · · Score: 1

      Although some data from the Palm LifeDrive (featuring a mecanical Microdrive CF module) could answer the drop-survivability in small form factor.

      Or, you know, iPods...

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    2. Re:Definitely not enough data by Anonymous Coward · · Score: 0

      1 single data

      The singular of data is datum. They managed to produce only 1 single datum.

  27. But Why? by Anonymous Coward · · Score: 0

    A lot of people have been posting what the "correct" metrics would have been to test the SSD drives vs traditional drives, which is fair.

    My question is why did the traditional drives outperform SSD drives in large data transfers? SSDs would have faster seek times as has been mentioned but I see no reason why a large file transfer would take longer on an SSD, anyone have insight?

    1. Re:But Why? by somersault · · Score: 1

      Because once the hard drive has 'seeked' its data, as long as the file it is reading is in one contiguous (un-interrupted) section of the hard disk, it can keep on reading without having to seek again. Think of it as having a car with low gearing as opposed to one with tall gearing - the lower gears let you accelerate faster but with a limited top speed, while in a high gear if you get on a straight, you can stay at your top speed (but if you hit a corner you have to slow right down then take a while to accelerate again). Got to love the car analogies ;)

      --
      which is totally what she said
    2. Re:But Why? by somersault · · Score: 1

      PS I'm not entirely sure why the SSD's 'top speed' would be slower than a hard drive's, but I think it's because you have to do the 'seek' time for each block of data you write - so even though the seek time is much faster (someone above mentioned 7500x faster than a HD I think) than a hard drives, you have to 'seek' for each block of data, whereas a hard drive only has to seek once and then can just get on with the reading/writing (as long as the file is uninterrupted). So say the SSD is limited by the time it takes to retrieve one byte - for a file 7500 bytes long the SSD would already be done returning it before the HD had started spitting out data, but for files over that length the HD can start to catch up. IRL it probably won't be 7500bytes, it will depend on how much data you read at a time from the devices. Is it obvious that I don't really have a clue about the low down technicalities yet? Just trying to help give an idea of what's going on though :p

      --
      which is totally what she said
  28. Weird test by The+Clockwork+Troll · · Score: 1

    I can't find an apples-to-apples comparison in this test.

    If they wanted to compare the best laptop mechanical drive to the best laptop drive (price no object), why didn't they use an MTron or Memoright drive (> 100MB/sec sustained read AND write)?

    If they wanted to compare the best laptop mechanical drive to the cheapest SSD drive, why didn't they use a Transcend drive ( $200)?

    --

    There are no karma whores, only moderation johns
    1. Re:Weird test by somersault · · Score: 1

      I can't find an apples-to-apples comparison in this test. You can't have RTFA then, because the test systems are both Apple Macbook Airs!! :p
      --
      which is totally what she said
  29. Vista for performance testing? by Matthew+Weigel · · Score: 1

    That just seems silly. I'd like to see performance tests on a system where the disk's performance affects the end result, rather than all of the results being homogenized by the operating system's poor I/O capability. Given Vista's adoption, it's not even a test of what disk performance will be like "in the real world."

    --
    --Matthew
  30. SSD Variation by ProfessionalCookie · · Score: 0

    I dunno if anyone's paying attention but SSDs vary hugely in speed- both random access and sustained transfers. It's pretty easy to find a slow SSD- they've been around forever. The Macbook currently uses a Samsung part.

  31. Sponsored by Seagate? by FlutterBoundary · · Score: 1

    I tried to read one of the other articles on the Computerworld website and was served a compulsory registration page - with a Seagate ad banner on it! One can't help but wonder if the reviewer's position might have been skewed a bit...

  32. What the reviewer did wrong. by Neoncow · · Score: 1
    So to sum up what the reviewer did wrong:
    • Only tested sustained write speeds.Has the impression that performance is copying multigigabyte files around all day.
    • Ignored the silence advantage.
    • Didn't consider power savings.
    • Didn't test seek speeds.
      When asked about ignoring the 20:1 advantage SSDs have in seek speed, responded:

      But keep in mind that it's only one component of the overall operation. These were all freshly formatted drives so fragmentation shouldn't be an issue and the longer the operation under that condition, the less it tends to matter.

      SSDs might even slow down slightly because some are built intelligently enough to not write to the same location each time (and thus prematurely "wear out" segments of memory which are, after all, limited use within context).
    • Comparing 3.5 inch 7200 rpm drives to 2.5 inch SSDs


    Anything else to add?
    1. Re:What the reviewer did wrong. by MushMouth · · Score: 1

      Chose low end ssd's

    2. Re:What the reviewer did wrong. by Anonymous+Custard · · Score: 1
      He failed to recognize that improved application start-up time heavily contributes to "system snappiness" ( http://www.anandtech.com/showdoc.aspx?i=3287&p=6 )

      I've been alluding to the SSD MacBook Pro feeling significantly quicker in overall usage...

      Application launch time contributes significantly to the snappiness of a system, and that's one area where the Memoright SSD excels.

      Take how long it takes to launch an application with the stock hard drive and cut it in half, because that's what the Memoright MR25.2-128S gives you. Boot time is also similarly reduced, it takes nearly 40 seconds to boot the stock MacBook Pro while the move to SSD brings it down to 22.
  33. Why are the results so bad? by Peter+H.S. · · Score: 1
    HD Tach test:

    Burst Speed Average Read Random Access CPU Utilization
    Crucial SSD 137.3MB/sec 120.7MB/sec 0.4ms 4%
     
    Barracuda HDD 135.0MB/sec 55.0MB/sec 13.4ms 4%
    BOOT UP TIMES (IN SECONDS)

    Cold Boot Restart
    Crucial SSD 39.9 78.4
    Barracuda HDD 39.9 59.9
    Yeah I know synthetic tests are problematic, but the two tests gives contrary results.
    Is it because a MS Vista boot and reboot doesn't involve much random R/W and therefore doesn't shows the appearrent strength of SSD's? Or is it because an extremely low random access value on SSD's are offset by the fact that sequential R/W's are rare on SSD's because of wear-level algorithms? Or is it something else? Twice the read speed and 30 times the random access time ought to give some advantage.

    --
    Regards
    1. Re:Why are the results so bad? by tknd · · Score: 1

      There's something wrong with the Vista boot and shutdown process because it seems slower than it needs to be. Anytime I have to restart or cold boot it takes considerably longer than a plain XP install. (Though XP tends to slow down over time as you add drivers, other software, and files get fragmented.) Vista boot kind of reminds me of Win2k, where nothing was optimized and everything happened sequentially even if it wasn't doing anything particularly useful (like timing out). My guess is vista is probably doing something stupid like waiting for each network interface to get assigned DHCP or something. Kinda like old linux distros that configured init and the network interfaces with DHCP to wait half a minute to a minute before they timed out.

      It isn't too much a problem since there's the sleep function which sleeps and wakes up within seconds. With the right hardware, power consumption in sleep mode is 1 or 2 watts more than when your computer is considered "off" (PSU still plugged in, so it is technically in standby). In fact the default shutdown option (little power button on the start menu) is to put the computer into sleep rather than shutdown. I guess they figured they didn't need to worry about boot and shutdown times if everyone just used the sleep function.

    2. Re:Why are the results so bad? by Sentry21 · · Score: 1

      Anytime I have to restart or cold boot it takes considerably longer than a plain XP install. I can attest to this. Every time I boot Vista, I say to myself 'Sheesh, I could have installed XP in the time this thing has taken.'
  34. Is Limited Number of Writes to SSDs a Problem? by Ron+Bennett · · Score: 1

    SSDs have greatly improved, and typically utilize wear leveling methods to more evenly distribute writes across memory cells.

    However, in real-world situations, do SSD write limitations ever pose a problem or is it a total non-issue these days?

    Ron

    1. Re:Is Limited Number of Writes to SSDs a Problem? by Dan+Ost · · Score: 1

      It's my understanding that SSD write limitations are a total non-issue with modern hardware.

      --

      *sigh* back to work...
  35. ya, so what? by zogger · · Score: 1

    The SSDs are getting better/cheaper/faster/larger all the time and part of the interest is that they are much more robust/less fragile and use a lot less electricity. [bad car analogy] A Ferrari is faster but it can't do the same work nor is as tough as the F450 we got, and I bet the F450 with the diesel engine gets better mileage while doing that work [/bad analogy]

  36. Reliability and shock resistance by Aram+Fingal · · Score: 1

    Flash media, like compact flash cards, are supposed to be very shock resistant compared to hard drives. That would give these SSD drives a big advantage in machines designed to be very rugged.

  37. The real improvement - resource contention by diamondsw · · Score: 1

    Completely missed the point. SSD's are not about extremely fast sequential access, they're designed for near-instantaneous random access. No seeking means faster random access, which also means MUCH improved performance when multiple processes are hitting the disk at once.

    Just think back to when you moved to a dual-core CPU how much more responsive it was. Now take that same jump to I/O, which is always the performance bottleneck. We're leaving the age of simple increases in horsepower - Mhz, RPM, and throughput; now we're attacking the problems of resource contention. Multicore CPU's, solid state disks, more memory, better CPU-memory interconnects - all of this is making resource contention and "churn" a thing of the past.

    --
    I don't know what kind of crack I was on, but I suspect it was decaf.
  38. Flash memory not true SSD tech by 0111+1110 · · Score: 1

    It is amazing to me that even other geeks have fallen for the corporate hype machine. This current gen of "SSD" has little to do with the actual promise of a solid state drive. Have you all forgotten the original point? We were getting tired of the slow incremental increase in speed that magnetic platter hard drive technology was giving us. Hard drives were and still are typically the bottleneck in many applications. They are what is holding us back from instant response times.

    These flash based drives are little more than a straw man or distraction from the true goal and promise of solid state drives. Gigabyte had the right idea with their I-Ram device but apparently they found making their own memory controller to be too difficult. That is something more appropriate for someone like Intel, they claimed. And I think this is actually a good point. So why aren't Intel and AMD pursuing such a device? I don't know the answer to that but I don't think it has anything to do with ability. Clearly Intel or AMD could make their own version of an I-Ram device that could have the potential to finally realize the dream and promise of the original solid state drive idea.

    The appeal of using a flash based drive for storing my data eludes me. Limited number of writes. Check. Unproven and highly suspect reliability (I have had several flash drives for my camera fail on me at unpredictable times). Check. No great speed advantage to the horribly slow archaic magnetic platter technology. Check. Expensive. Check. Sounds great. Really.

    It is the 21st century already and not only do we not have HAL 9000 computers or replicants or flying cars or lunar vacation spots or fusion, but we don't yet even have drives that are significantly faster than they were 20 years ago. I am sitting here tapping my fingers on my desk waiting for the revolution in data storage that surely must be just around the corner. I am sorry but these flash based SSDs are not it.

    --
    Quite an experience to live in fear, isn't it? That's what it is to be a slave.
    1. Re:Flash memory not true SSD tech by owlstead · · Score: 1

      Well, the problem with RAM is that it doesn't really hold state. Of course, you can keep it powered using battery, but would you give up so much reliability for a speed advantage? And RAM takes power all the time. This is fine if your server gets accessed all the time, but otherwise it is a waist of energy.

      Also, even though prices are now fairly low, RAM is as expensive now as a flash SSD. That sounds reasonable, but remember the energy advantage of flash. Also think of the fact that flash memory as used in SSD drives has a very high price point compared with USB flash drives and Compact Flash. Sure, this is normally cheaper flash, but the difference cannot be *that* huge.

      But most importantly: check the speed in which flash is getting bigger and cheaper. RAM is nowhere near this curve. PRAM also holds many promises, even though speculating on memory technology is a very risky thing to do. RAM won't be able to keep up. There are many more devices that need loads of flash compared to those that need RAM.

      Finally, Intel and AMD are making chips for RAM drives. They are called chip sets (or, in case of AMD, processors) and are normally a feature of a motherboard you buy. This may sound like trolling, but most OS use the memory that is left after the processes have grabbed as much as they need as disk cache. This is actually quite near the idea of a RAM drive backed by a hard disk. This RAM drive has got a *very* speedy connection to the processor as well, beats the hell out of (S)-ATA.

    2. Re:Flash memory not true SSD tech by Sentry21 · · Score: 1

      Gigabyte had the right idea with their I-Ram device [wikipedia.org] but apparently they found making their own memory controller to be too difficult. That is something more appropriate for someone like Intel, they claimed. And I think this is actually a good point. So why aren't Intel and AMD pursuing such a device? What would be even better is if they could take a disk, or array of disks, and then stick some memory in front of that â" say, 512 MB â" that they could use to buffer reads/writes right on the disk controller. It would be a problem if you lost data, though, but you could stick a battery on it, so that if the power died, you could still complete the last few writes once power was restored.

      I know I must be tired, because this was literally my thought process, until I realized I'd just (re-)invented the battery-backed write cache. Still, this is a far more practical option, and it's entirely possible (though it would be expensive) to implement this even in a laptop, to buffer reads/writes over time.

      I know that in most cases, my HD is almost completely idle, so in those few cases where I burst far beyond what my HD is capable of, it would balance out in not too long, and quite possibly improve performance, at least for writes. For reads, it could be improved by using the potential for parallelism that SSDs offer, by being able to read multiple blocks in parallel, rather than in sequence like normal HDDs require, and then buffer that directly into memory.
  39. Performance RAID by SpryGuy · · Score: 1

    In other tests I've seen, the only time the SSD drives come out on top is when configured in performance RAID style, so that writes are parallelized across two or more SSD units.

    If someone could put together a convenient RAID type package, the extra cost might actually result in extra, noticable speed improvements, even for writes. And two 64GB SSD units arranged in a performance RAID package would give a more usable 128GB "hard disk" to store things on anyway.

    --

    - Spryguy
    There are three kinds of people in this world: those that can count and those that can't
  40. Speed is a subset of performance... by RJFerret · · Score: 1

    They didn't test performance, but speed. One of the biggest aspects of "performance" is efficiency. Despite talking about some aspects of performance in the article, "Having no moving parts is, naturally, important. ... in theory -- should use less power than equivalent mechanical hard drives."

    Testing speed alone ignores the different applications for the different products!

  41. MTBF by weave · · Score: 1

    All I care about is MTBF. I am so sick and tired of trying to get data off of crashed drives and restoring computers for family members (and myself) . Even with current backups, it's a hassle and disks fail at the most inconvenient time.

    My wife wanted a laptop recently and I made her spend the extra money for an SSD.

    1. Re:MTBF by 0111+1110 · · Score: 1

      All I care about is MTBF. I am so sick and tired of trying to get data off of crashed drives and restoring computers for family members (and myself) . Even with current backups, it's a hassle and disks fail at the most inconvenient time. I have had much more frequent and less predictable failures from flash drives than from hard drives. Granted it is not a completely fair comparison since the flash drives were being used in portable applications (i.e. cameras) and the hard drives were sitting comfortably in my computer case. However I am less than impressed with what I have seen of flash drive reliability. I have been using the same Seagate hard drive for a system drive for the last 10 years. Can any frequently used flash drive ever hope to store your data reliably for that length of time? Wear leveling my ass. You want to trust your data to unproven wear leveling schemes be my guest. Just don't complain when your data just disappears one day with no hope of recovery. That's another advantage to hard drives. At least you can get data off of a failing hard drive. This ability to gracefully/gradually fail so that you have a chance at recovering your data is not a bug, but a feature. One that you may be taking for granted.
      --
      Quite an experience to live in fear, isn't it? That's what it is to be a slave.
  42. Native command queuing with newer SATA drives by rlk · · Score: 1

    As others have said, using these things with streaming I/O doesn't make much sense.

    I recently built myself a new system. The new processor (Xeon E3110, aka Core 2 Duo E8400) certainly did make boot time somewhat faster, but not dramatically so. Likewise for initial login -- the KDE desktop came up somewhat faster, but it wasn't overwhelming.

    Then it occurred to me to move my root and home directory partitions from an older 250 GB 1.5 Gb/sec SATA drive to my newer 500 GB 3.0 Gb/sec compatible drive. There are more differences than just the interface speed; the most notable one is probably Native Command Queuing. This is similar to tagged command queuing on SCSI; it allows the host to queue multiple commands to the disk, which replies to 'em as ready.

    *That* made a difference.

    fsck insists on checking the partitions one at a time (it sequences the partitions on a particular disk even if you tell it otherwise in /etc/fstab), and it's single threaded and does no async I/O. Reiserfs check does a quick scan of the filesystem tree, which seems to take time proportional to the size of the partition, so that didn't really change very much. After that, it's a completely different story. The rest of the boot sequence now completes in maybe 10 seconds, tops (it previously took something like a minute), and login to my KDE desktop (even including Firefox) really is fast -- only a bit slower than a warm login, when everything's in memory.
    The issue's not lack of memory -- I had 2 GB on my old system and 4 GB now, and anyway, the big change was on my new system only when I switched drives around.

    Moral of the story: if you're suffering from slow boot, make sure that your motherboard supports SATA 3.0 Gb/sec, use AHCI and native IDE (not legacy IDE), and make sure that your drive supports SATA 3.0 Gb/sec and that it isn't jumpered for 1.5 Gb/sec.

  43. Test protocol by Yvanhoe · · Score: 1

    1. Drop both drives from a 3 meters height. 2. Do the test again 3. Repeat until one disk has performance problems.

    --
    The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
  44. Noise level on new 2.5" drives ... by trolltalk.com · · Score: 1

    I can't hear the hd on my laptop, and I rarely hear the fan. The newest 2.5" drives are super-quiet.

  45. Those Who Write by fm6 · · Score: 1

    Write speed may be irrelevant to the applications you happen to run. But it's pretty relevant to your OS.

    1. Re:Those Who Write by thePowerOfGrayskull · · Score: 1

      Unless you disable virtual memory... contrary to popular myth, doing this on Windows does not have any negative effects if you're running applications written in the last 10 years or so. It actually speeds up performance noticeable, since Windows does a horrible job at managing swap space.

    2. Re:Those Who Write by pipatron · · Score: 1

      I haven't used any swapspace for years on my desktops, memory is so cheap now that there's no point. On my servers, of course, but then again it's 99.9% unused.

      For example, this thinkpad has 1.25GB RAM, and I've seen at most 300MB used. Then again, I don't run Vista.

      --
      c++; /* this makes c bigger but returns the old value */
    3. Re:Those Who Write by Bishop+Rook · · Score: 1

      Write speed may be irrelevant to the applications you happen to run. But it's pretty relevant to your OS. Ironically enough, seek time is much more relevant to virtual memory paging performance than linear read/write throughput. Which is why your computer gets a not-too-modest speedup using a flash drive for virtual memory.
    4. Re:Those Who Write by Captain+Splendid · · Score: 1

      Disabling virtual memory on Windows is doable but not foolproof. For starters, don't bother if you have at least 1GB of RAM (more is very preferable), and be ready for Windows to die on you once in a while with no warning. (I know, I know, what's new about that?

      --
      Linux, you magnificent bastard, I read the fucking manual!
    5. Re:Those Who Write by winkydink · · Score: 2, Funny

      I haven't used any swapspace for years on my desktops, memory is so cheap now that there's no point. On my servers, of course, but then again it's 99.9% unused.

      For example, this thinkpad has 1.25GB RAM, and I've seen at most 300MB used. Then again, I don't run Vista.

      You don't run Firefox either then..

      --

      "I'd rather be a lightning rod than a seismometer." -Ken Kesey

    6. Re:Those Who Write by thePowerOfGrayskull · · Score: 1

      I should have mentioned that - given the apps I run, I wouldn't even try it with less than 2GB. Haven't had any sudden death issues though.

  46. Better disable atime if using SSD by Anonymous Coward · · Score: 0

    You better disable atime if you're using SSD drives or you'll find they don't last as long as you would expect.

  47. Crappy SSDs to test by MushMouth · · Score: 1

    It would be nice if the SSDs they tested were actual high performance models, instead of crappy cut rate ones. They should do the same test with Samsung, Sandisk, and MTron drives. As it was these crappy disks destroyed the mechanical disks in IOps.

  48. Speed? WTF? by Yvan256 · · Score: 1

    Right now, using SSD is not about saving money or having a faster drive (unless your other choice is an 1.8" drive, like the MacBook Air).

    SSD is supposed to be about power savings, which should be one of your top priorities when designing a portable device (see also Nintendo GameBoy vs Sega GameGear).

  49. who cares by thetoadwarrior · · Score: 1

    The point of SSD drives, imo, is the fact it makes a laptop more portable as in the fact it's safer to carry around without worrying about the hard drive head crashing into the disk because your bus vibrates or because you moved it.

    I don't care what the write speed is if it's safer while I'm walking about with it.

  50. Apples to Oranges by camperdave · · Score: 1

    It strikes me that current magnetic hard drives have rather huge memory caches for buffering data. The Baracuda drives cited in the article have 16 MBytes worth. Yet there are no cache specs listed for the solid state drives. This could mean that the solid state drives are writing directly to the media. I wonder how well the solid state drives would perform relative to magnetic hard drives that had their caching disabled (or conversely if you had a 16MByte cache for the solid state drive).

    --
    When our name is on the back of your car, we're behind you all the way!
    1. Re:Apples to Oranges by Belial6 · · Score: 2, Insightful

      Huh. I've always thought that the cache on Hard drives was amazingly small. 16MB? Heck, give me a drive with at least a gigabyte of cache. When I boot up my computer, it should just start reading any sectors that have been used frequently.

    2. Re:Apples to Oranges by Bishop+Rook · · Score: 1

      SSD drives don't require a cache, because the entire drive is cache. The 32GB of the SSD has roughly the same performance profile as the 16MB cache on a magnetic drive. Disable cache on a magnetic drive, and the tests from TFA would produce the same results--since they're measuring raw read/write throughput and random-access seek time. The really important test would be checking the seek time on one frequently-used area of disk. You'd see an improvement in the average seek time when the drive's caching is enabled, as compared to having no cache. The ironic thing is, this is the most important test in real-world performance, because caching speeds up the average seek time for frequently-accessed virtual memory pages.

    3. Re:Apples to Oranges by makapuf · · Score: 1

      why pay for ram in your HD that only can be useful for it when you could buy multi purpose normal ram which is user extensible, cheap, and used by the OS when it is useful for caching and used by apps when they need it ?

    4. Re:Apples to Oranges by Anonymous Coward · · Score: 1, Informative

      Huh. I've always thought that the cache on Hard drives was amazingly small. 16MB? Heck, give me a drive with at least a gigabyte of cache. When I boot up my computer, it should just start reading any sectors that have been used frequently. That is, at least theoretically, what Vista does by using your main system RAM.
    5. Re:Apples to Oranges by drinkypoo · · Score: 1

      SSD drives don't require a cache, because the entire drive is cache. The 32GB of the SSD has roughly the same performance profile as the 16MB cache on a magnetic drive.

      The flash in the SSD is as fast as DRAM cache on a magnetic disk? Go on, pull the other one.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:Apples to Oranges by Bishop+Rook · · Score: 1

      The flash in the SSD is as fast as DRAM cache on a magnetic disk? Go on, pull the other one. Not as fast, but roughly the same performance profile--most importantly the extremely fast access time. When you've already cut the random access time down to 0.4 ms by using flash, as in TFA, you don't get a whole lot of benefit adding a few megs of DRAM cache to trim another few microseconds off the average seek. Magnetic disks need the cache to improve their dismal average access time, SSDs simply don't.
    7. Re:Apples to Oranges by drinkypoo · · Score: 1

      No, but you could probably benefit from having a sizable write cache on the disk, because flash has poor write times.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    8. Re:Apples to Oranges by Bishop+Rook · · Score: 1

      Fair enough, though flash random-write latency has been improving drastically in recent years. Latest stuff in development from Intel and Micron supposedly has a random write latency of 1.5ms (at least, that's what they list for typical 'erase performance' which ought to mean doing a full write of an erase block). Let's just hope it isn't ridiculously expensive when it comes out.

    9. Re:Apples to Oranges by k8to · · Score: 1

      Though at that point you can just use system dram as a write cache... I don't really grasp this one.

      --
      -josh
    10. Re:Apples to Oranges by drinkypoo · · Score: 1

      RAM cache reduces access times even further, and protects the flash memory from small random writes when the filesystem sector size is not equal to the flash memory sector size.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  51. anybody else... by thrillhouse13 · · Score: 1

    ...prefer reading stats like this in a damn bar graph or something?

  52. What about Altitude by wjsteele · · Score: 1

    For years, us pilots have been looking for a viable way of taking data to altitude. Typical hard drives fail at altitudes above ~15,000 feet. SSDs have basically eliminated that problem altogether.

    Using SSDs on our portables, we can now go to extreme altitudes in unpressureized enclosures without the fear of drive failure.

    Bill

    --
    It's my Sig and you can't have it. Mine! All Mine!
  53. FUD by MushMouth · · Score: 2, Informative

    Wrong, this myth simply will not go away. All modern drives have write leveling technology built in. Also unlike a mechanical drive which generally fails on read, SSDs fail on write which allows the drive itself to trap all failures, and redirect the bytes to another unused sector. Anyone who care about performance shuts off atime as it is.

  54. Re:worse than XP, they used Vista and a bad drive. by Anonymous Coward · · Score: 0
    coppies

    Hi twitter.

    This "Mactrope" sockpuppet is now posting at -1. That makes five ruined Slashdot accounts so far.

    As to the actual contents of your post, well, as usual it just boils down to "I hate Microsoft". No attempt at rational thought or discussion, intentionally misrepresenting what the article said and so on. Nothing new.

  55. FUD all current ssd's have write leveling by MushMouth · · Score: 1

    All drives that have been release in the last 2 years have built in write leveling technology which pushes the bytes to new physical locations in memory. Hence it now takes something on the order of 100 years of constant writing to "wear" out the drive.

  56. bad summary by superwiz · · Score: 1

    I don't know if the test took this into account, but the summary only describes throughput performance. But most HD access is burst. And it doesn't mention whether that's faster or not.

    --
    Any guest worker system is indistinguishable from indentured servitude.
  57. And some drop tests, and airport scaner tests, and by celtic_hackr · · Score: 1

    Let's not get too excited or too under-excited about SSDs until we have done some serious comparisons.

    I'd like to know:
    1: How fast are they at reading in a bunch of data fragmented over a good size area (not a concern for me, thank you EXT3),
    2: How reliable are they at holding the data, ie what is the decay rate for the data compared to a HD,
    3: how would they satnd up to repeated exposure to airport and other scanning equipemnt vs HDs,
    4: How high can you drop a laptop with each type of drive, and what kind of other travel related shock,
    5: How sensitive is a SSD compared to a HD in regards to say static electricity.

    I'd say the article's author is only doing a very narrow comparison of pros and cons of SSDs vs HD. I'd be willing to spend some serious bucks on a hotplug SSD for backup purposes, or even for extendable space. After all, it wouldn't take much to build a nice little "disk" from sticks that would be "hot-pluggable" in any PC with a usb slot. Quick-N-Dirty disk: take one 4 (6, 8, ...) port usb hub, add 4 (6, 8, ...) 8GB usb sticks and voila a 32 (48, 64, ...) GB drive although you'd have to use RAID or mount points (in Linux), or something to combine them. Now what we need is someone to build a pluggable case that has an internal card that combines the sticks installed into a single disk from the visible USB port. Then, where's your agurment SSDs aren't worth the cost? I'd like to see you hotswap an HD platter.
    Damn, that's such a good Idea, I should have implemented it myself and marketed it, now someone is going to read this and "steal" my Idea and make ...

    PROFIT!

  58. "Solid state"? by Anonymous Coward · · Score: 0

    As opposed to what? The hard disk's vacuum or gaseous storage? When did "solid state" go from a technical term with a precise meaning to "no moving parts"?

  59. Re:HD-DVD by whackco · · Score: 1

    What is this HD-DVD you speak of?

  60. How Flash SSDs Work and How They Can Work Better by DDumitru · · Score: 3, Informative

    My apologies for a long post. There will be some adverts embedded, but I will try to keep things informative.

    The reason that Flash SSDs act "wierd" in benchmarks is that they have asymmetric performance patterns when reading and writing. Particularly with random operations, this asymmetry is huge. Here are a couple of example "drives":

    * Mtron 7000 series: >14,000 4K random reads. ~130 4K random writes.
    * SanDisk 5000 series: ~7,000 4K random reads. 13 4K random writes.
    * Cheap CF card or USB stick: ~2,500 4K random reads. 3.3 4K random writes.

    This is a 100:1 performance deficit when doing random writes versus the random reads. This has some really weird impacts on system performance. For example, if you run Outlook and tell it to "index" your system, it will build a 1-4 GB index file in-place with 100% random writes. If you do this on a hard disk, the job takes a long time and drags down your laptop, but the operation is still pretty smooth. Do the same think on an SSD and the system slugs to molasses. One of our customers described it as "totally unusable" with 2+ minutes to bring up task manager. What happens is that the fast reads allow the application to dirty write buffer faster and this then swamps system RAM, you get a 100+ deep write queue (at 13/sec), and you want to throw the machine off of a bridge.

    This fix as some have described it is not some magic new controller glue or putting the flash closer to the CPU. It is organizing the write patterns to more closely match what the Flash chips are good at. Numerous embedded file systems like JFFS do this, but they are really designed for very small devices and are more concerned with wear and lifespan issue than performance.

    Now here comes the advert (flames welcome). A little over 2 years ago, I wrote a "block translation" layer for use with Flash storage devices. It is somewhat similar to a LogFS, but it is not really a file system and it does not play be all of the rules of a LogFS. It does however remap blocks and linearize writes. Thus it plays well with Flash. It also appears to be an "invention", and thus my patent lawyer is well paid.

    The working name of the driver layer itself is "Fast Block Device" (fbd) and the marketing name is "Manged Flash Technology". And what this does is to transparently map one block device into another view. You can then put whatever file system you want into the mix.

    In terms of performance, it is all about bandwidth. Build a little raid-5 array with 4 Mtron drives and you will get over 200 MB/sec of sustained write throughput. With MFT in place, this directly translates into 50,000 4K random writes/sec. Even better, you tend to end up with something that is much closer to symmetric in terms of random read/write performance.

    MFT is production on Linux (it has actually been shipping since last summer) and is in Beta test on Windows. It works with single drives as well as small to medium sized arrays. It does work with large arrays, but the controllers don't tend to keep up with the drives, so large arrays are useful for capacity but don't really help performance a lot. Once you get to 50,000 IOPS it is hard for the controllers to go much faster.

    Consumer testing with MFT tends to produce some laughable results. We ran PCMark05's disk test on it and produced numbers in the 250K range. This was with a single Mtron 3025. Our code is fast, but we fooled the benchmark in this case.

    There are several white papers on MFT posted in the news link of our website:

        http://managedflash.com/

    My apologies for the advert, but I see a lot of talk about SSDs without actually knowing what is going on inside.

    I am happy to answer any questions on-line of off.

    Doug Dumitru
    EasyCo LLC
    610 237-2000 x43
    http://easyco.com/
    http://managedflash.com/
    http://mtron.easyco.com/

  61. hey, best of both worlds! by simplerThanPossible · · Score: 1
    write to HDD; SDD for reading...


    HDD -> SDD in the background. There's data inconsistency, but it's a form of caching, so I expect there's already an efficient solution.

  62. I wish the Air was a totally different design by sootman · · Score: 1

    I've seen the MacBook Air in person and it is an amazing design. It really is incredible how light it is. That said, it's pricey (not that Apple minds that) and what I really wish they would have made would have been...
    - 10 or 11" screen
    - 8 or 16 GB solid-state drive--for a secondary machine which WON'T be used for lots of DV capture, storing your whole iTunes library, etc., a small drive is fine
    - built-in CF reader, and you could get a big CF card to be used as a TimeMachine volume

    In other news, I do have a (non-Pro, non-Air) MacBook and the drive is ridicuously easy to get in and out. (Remove the battery, loosen three captive screws, pull away the L-shaped piece of metal, slide out the drive) and I'd like to experiment with some kind of SSD, either a 'proper' drive or a CF/SD/whatever card in a SATA adapter. Any suggestions on where to start? A newegg search for 'sata ssd' shows an 8 GB unit for $210 and a 16 GB one for $340. Searching for 'sata cf adapter' shows a $40 unit--could I just get one of those and a fast CF card? This page ends with the conclusion "A serious SSD a CompactFlash card is not" but it is from 2000 (but then again, shows as being updated a just a few months ago. I've written to the author.) Any thoughts?

    --
    Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
  63. Re:And some drop tests, and airport scaner tests, by CommanderData · · Score: 3, Informative

    Well, I can supply my own experiences for you, after using a 32GB Samsung SSD for a year, and a 64GB Samsung SSD for several months...

    1) Mine have been formatted NTFS, running Windows XP (and additionally Apple HFS Journaled recently when experimenting with OS X). I do not defragment the SSD, there is no point. Read speeds have always been better than write speed, but I see no difference in performance over time.
    2) Both of the drives I have are fully functional, even though I abused the 32GB one mercilessly. That laptop has only 1GB of RAM and I would run so many programs that things were swapping constantly for the past year.
    3) The 32GB SSD has been through airport scanners approximately 50 times now, no problems. The 64GB is too new, only travelled a few times so far.
    4) My laptops are always on the go, brought into many factories as a consultant. While in my bag it has taken falls down sets of stairs. The laptop itself (a Fujitsu P1610) has been dropped from a height of 3.5 to 4 feet onto a metal catwalk while running with no adverse affects (other than a few scuffs and dents on the corners).
    5) Not sure how well they stand up to static, but it has stood up well to a variety of high EM fields, and high/low temperatures. No data loss. I have had regular hard disks die from working next to large transformers (and their magnetic fields) for an afternoon.

    Hope that helps you. For my line of work, they have been incredible. I used to go through 3 or 4 laptop hard disks per year due to various issues. Now the only reason I bought the 64GB SSD is increased storage capacity.

    --
    Urge to post... fading... fading... RISING!... fading... fading... gone.
  64. Try again with linux and the noop IO Scheduler... by Anonymous Coward · · Score: 0

    Remove the default anticipatory scheduler (which is good for mechanical drives... not so much for flash) and you'd probably get much better results with SDD.

    cd /sys/block/hda/queue
    echo noop > scheduler

  65. A resounding "Wha?" by Orig_Club_Soda · · Score: 0

    Waht about battery time. Shouldn't a SSD save on battery usage?

  66. Tried more SSD's? by Anonymous Coward · · Score: 0

    A major point of contention on this matter is the type of SSD. SSD technology has a very wide gap in performance, largely based on manufacturer.

    I work for an SSD distributor, and it's a known fact that Crucial an d RiData SSD's simply do not perform as well as Mtron or Memoright drives. Also, OCz drives have narrowed the gap considerably.

    So before you crucify SSD's as a whole, get a larger sample size.

    To argue on the other hand of this, WD HDD's such as the Raptor and the new Velociraptor have much higher speeds than the Seagate drives, so a more comprehensive comparison is needed.

  67. Solutions for hybrid disk setups? by dubl-u · · Score: 2, Interesting

    If they really wanted to test SSD performance they would have taken Linux with jffs2 or newer logfs. Does anybody have a decent solution for using a flash drive to boost performance of a regular drive?

    I just ordered a new laptop, and it has an ExpressCard slot into which I could drop 4 or 8 GB of solid-state disk at a reasonable price. That could serve as a giant cache, one that unlike RAM could be safely used as a write cache.

    It seems like there would be a clever way to treat the SSD plus the regular hard drive as one unit so that the hard drive could be spun down for hours of normal working situations, giving a giant extension of battery life.

    Anybody heard of a virtual block device or special filesystem that would take advantage of this in Linux?
    1. Re:Solutions for hybrid disk setups? by Sentry21 · · Score: 1

      Put your paging file and filesystem journal on the SSD. The paging file won't get huge bulk read performance (see the article), but when paging in blocks from all over the place, it should be reasonable, and won't clog up your disk's throughput. The FS journal is the same idea - you don't need throughput, but the journal keeps getting read/re-read/written/re-written, so having something that doesn't involve writing to the platter then fetching back off it could boost performance to some degree.

      Benchmarks are probably out there, but I'm sleepy.

  68. Re:How Flash SSDs Work and How They Can Work Bette by Chandon+Seldon · · Score: 0, Flamebait

    It also appears to be an "invention", and thus my patent lawyer is well paid.

    Good job. Now

    1. No one will use your stuff.
    2. There's a legal obstacle to anyone else trying to solve the same problem.

    So... if your actions have any effect at all, it will be to delay the development of software that effectively uses SSDs.

    --
    -- The act of censorship is always worse than whatever is being censored. Always.
  69. They used slow SSD's by no-neo777 · · Score: 1

    They weren't using the fastest sata SSD's readily available, so I'm not too surprised by the results. There's an SSD on newegg from OCZ that can do 100MB/s read and 80MB/s write. Also, you can easily find MTRON 2.5" sata drives that can do 120MB/s read 90MB/s write. All similarly or better priced.

  70. Re:worse than XP, they used Vista and a bad drive. by Anonymous Coward · · Score: 0

    Look, we get it. You hate twitter. The rest of us don't care. Shut the fuck up.

  71. Re:And some drop tests, and airport scaner tests, by Anonymous Coward · · Score: 0

    Good questions.

    1) Seek time is 0 for flash. The HDD will be faster on a fresh install than after filesystems get fragmented.

    2) Retention for flash is rated as long as life for HDD. Typical disk lifetime spec is only 5 years due to mechanical parts.

    3) Energy to flip a bit is much higher for HDD than flash, but both have ECC and use totally different base technology. Its a good Sophomore Physics problem.

    4) Flash wins. HDD spec is 250 Gs for 2 msec.

    5) Once components are soldered to a PCB they are a lot less sensitive to handling. HDD and SSD should both be handled only by the cases, and both have exposed components.

    I already know of one flash SSD using "your" idea. Conventional USB flash controller chips cost $0.30 in large quantity. A SATA-to-8-port-USB chip in front makes a flash drive.

  72. 2nd Gen SSD benchmarks. by v(*_*)vvvv · · Score: 2, Informative

    All the brand notebooks with SSD options use first generation SSDs. These have the shattering access speeds, high durability, no noise, and power efficient benefits, but read/write performance is still mediocre.

    The second generation SSDs would cost you more than a whole notebook, but have significant performance improvements:

    Memoright GT vs Mtron vs Raptor vs Seagate

    Memoright nails it. It is easily twice as fast as what Mac puts in their notebooks.

    If you *really* want an SSD, buy one separately and install it yourself. You will not be disappointed.

    BTW the file indexing that causes SSDs to slow cause HDDs to slow as well. Many people have reported unbearable slowdown, and that is with HDDs. I am sure anything slower than that would make you want to return the whole thing, but this can be fixed. Most people will tell you to just turn it off. Google has also complainted about Microsoft pre-installing an indexing system that sucks.

  73. Re:How Flash SSDs Work and How They Can Work Bette by Bazouel · · Score: 1

    Looks promising ... but I would divert some money from your lawyer to your website design if I was you ;)

    --
    Intelligence shared is intelligence squared.
  74. Cheap SSD style performance from USB Flash Drives by AganLex · · Score: 1

    I just recently did some raw read/write speed tests with a raid0 of a bunch of USB Flash Drives. The price for performance ratio is really good compared to standard SSDs.

    I've got it up on my site here.
    6x USB Flash Drive Raid

  75. Re:How Flash SSDs Work and How They Can Work Bette by DDumitru · · Score: 1

    Its what happens when techies run a company rather than marketeers.

  76. Your mileage may vary. by Explo · · Score: 1

    Since I bough my first digital camera in 2002, I've taken more than 40000 photos and have yet to lose any photos due to a memory card failure. Of the 5 cards I own, I still use 3 frequently (the 32 MB and 128 MB ones are a tad small these days, especially when shooting RAW). Perhaps it's been dirt/wear on the card connectors rather than actual flash failure in your case?

    --
    Everyone who makes generalizations should be shot.
  77. Economies of Scale by mebrahim · · Score: 1

    Economies of scale will change the situation soon.

  78. Dammit Stripe Them Already! by dwalsh · · Score: 1

    Internally, the drives should be configured as several banks of flash memory with their own read controllers. Then the drive can stripe the data across those banks (like a RAID array) for huge boost in sustained read/write speed.

    The cool thing about this is you can have as many banks and controllers as you are willing to pay for, so you can scale up the throughput almost as much as you like.

    From the outside, the drive would appear as a normal single drive.

    --
    ${YEAR+1} is going to be the year of Linux on the desktop!
  79. Test the real slowdowns by turing_m · · Score: 1

    I would have loved to have seen the difference in seconds between SSD and HDD in the following:
    -openoffice load time
    -time to switch a tab in firefox
    -time to switch or minimize a window
    -boot time
    -loading a large spreadsheet

    Preferably, times between a fast and a slow CPU should be compared.

    Those are the only areas of obvious slowness I see on a day to day basis on my 4 year old laptop, and they all strike me as bottlenecked by random access rather than CPU. I don't think any of those applications involved reading a long contiguous file like a DVD for example.

    It might turn out that if you want to upgrade, you might get away with just a switch to SSD for the most noticeable speed improvement for the price; from what I have found, anything beyond the first 10 Gb is luxury in the form of music, photos or movies. So you really don't need an 80Gb drive for that application.

    --
    If I have seen further it is by stealing the Intellectual Property of giants.
    1. Re:Test the real slowdowns by phantomcircuit · · Score: 1

      -openoffice load time They did test this. OpenOffice load time is a sequential read of files
      -time to switch a tab in firefoxThat is done entirely in memory, the HDD makes no difference
      -time to switch or minimize a windowall memory, same as above
      -boot timeFor a correctly designed operating system this should be sequential, although it can sometime be random (ie testing this is irrelevent because it differs by the OS)
      -loading a large spreadsheetAgain they did test this as it is a sequential read
      Preferably, times between a fast and a slow CPU should be compared.Why?
  80. Native SATA SSD by shird · · Score: 1

    http://lenovoblogs.com/insidethebox/?p=141

    From the above article : "Also ask if the drive is a native SATA implementation or a parallel drive with a SATA bridge chip. You want the native SATA implementation. Theyre better in all aspects."

    Apple uses the bridge chip, Lenovo uses the native implementation. I'm sure this would be a factor in their results.

    Disclaimer: I shelled out a fortune for a Lenovo x300 with a SSD.

    --
    I.O.U One Sig.
  81. Re:And some drop tests, and airport scaner tests, by TheRaven64 · · Score: 1

    1: How fast are they at reading in a bunch of data fragmented over a good size area (not a concern for me, thank you EXT3), UFS-like filesystems, including ext3, proect you from internal fragmentation to a degree. It's still possible, and becomes more probable the closer the disk gets to being full, it's just not the default as it was with FAT. It won't protect you at all from related files being in different parts of the disk. Launching an application which accesses a load of resource files, shared libraries, and so on, will result in a lot of disk seeks.
    --
    I am TheRaven on Soylent News
  82. Re:HD-DVD by SanityInAnarchy · · Score: 1

    Habit. I used to develop for HD-DVD, and I'm still bitter enough to bring it up in every Blu-Ray discussion.

    I mean "in every high-def discussion."

    Fuck.

    --
    Don't thank God, thank a doctor!
  83. Also, Consider This by Anonymous Coward · · Score: 0

    The power consumption as people already mentioned.

    Also, look at the weight. This thing shaves off a pound of weight.

    Suddenly, you go from 6lbs to 5lbs for a high performance laptop. Thats huge.

  84. difference between removable flash drive and SSD? by dupersuper · · Score: 1

    what is the difference between removable flash drives (CF, SD, thumbdrives) and SSD that causes the big price difference?

  85. I only mentioned EXT3 as an example by celtic_hackr · · Score: 1

    I'm aware of the other filesystems that do internal defragging, but since EXT3 is what I use (I used to use Reiser) that is where my example came from. I was really just trying to point out that the posting author missed a lot of the pros of SSD drives. The time to seek anywhere on a flash disk is the same, whereas on a platter it depends on where in the ring it is located. I'd say the article actually got it wrong. If I had the extra cash to spend, it'd be SSD for sure. I'm still waiting for it to come down a bit more. Although I may take the time to hack up a little project and build my own expandable one and "grow" some new drives over time with mad money. I've been looking for a good pic and usb project, and this fits the bill nicely.