Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Which OS Performs Best With SSDs?

Posted by CmdrTaco on Thu Dec 11, 2008 11:46 AM
from the io-io-it's-off-to-work-we-go dept.
Lucas123 writes "Linux, Vista and Mac OS perform differently with solid state disks. While all of them work well with SSDs, as they write data more efficiently or run fewer applications in the background than XP, surprisingly Windows 2000 appears to be the winner when it comes to performance. However, no OS has yet been optimized to work with SSDs. This lost opportunity is one Microsoft plans to address with Windows 7; Apple, too, is likely to upgrade its platform soon for better SSD performance."
+ -
story

Related Stories

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • They didn't compare anything to Linux, so I just have one question:

    How easy would it be to modify Windows 2000 to be even better? Replace the file systems, alter the way the kernel writes to the drive, etc?

    • Re: (Score:3, Insightful)

      by Malc (1751)

      What is your criteria for a different file system? NTFS is already a very good one for most of the important criteria.

        • by Anonymous Coward on Thursday December 11 2008, @12:04PM (#26076819)

          for when you need to partition your wife

        • by JCSoRocks (1142053) on Thursday December 11 2008, @12:08PM (#26076869)
          Actually recent benchmarks have shown that defragging doesn't make *that* much of a difference - http://www.maximumpc.com/article/the_disk_defrag_difference?page=0%2C2 [maximumpc.com] I've never heard of a fragmented drive affecting machine stability. That's like saying having a 5400 RPM drive instead of a 10,000 RPM drive in a server will make it crash... It makes no sense. Fragmentation has nothing to do with data integrity which is the only thing that would affect stability.

          Also, it's "its" not "it's".
          • Re: (Score:3, Interesting)

            by ADRA (37398)

            Fragmentation causes more needle shifts than regular burst read/writes. If a hard-drive is most likely to die from needle shifts, fragmentation could wear on the drive more than a nice and tidy system.

            Of course this is all speculation and moving the needle could have absolutely nothing to do with death rates, who knows.

          • by ThePhilips (752041) on Thursday December 11 2008, @12:29PM (#26077173) Homepage Journal

            LOL.

            I had in past run a Windows server for about 2 years. And it was terribly slow, despite the fact that in the beginning it was blazingly fast. I believe it was O&O Defrag which actually returned the server to life: downtime on Sunday with boot time defragmentation did the miracle.

            Same thing in the company I work for right now: IT recently took off net two file servers and exchange server to defragment file systems, because FS performance went considerably down. Folks have said that they "lose to fragmentation 30% of FS performance," meaning that system works about twice faster after defragmentation. That's why they schedule at least one down time for every windows server in company.

            Whatever synthetic benchmarks people perform - it is irrelevant.

            Long term real life experience tells otherwise.

          • Re: (Score:3, Insightful)

            depends on your definition of crash. Having a slower HD will cause disk IO to stack under heavy load. What is the real difference between a server that has crashed, and one that doesn't respond? Fragmented disks will have the possibility of a similar effect. The linked article measures the difference between a disk that is 7.5% fragmented and after its been defragged. 7.5% isn't much. It really depends upon which files have been fragmented. If they are rarely accessed data files, then obviously there isn't
    • Re: (Score:3, Informative)

      Linux will have good support SSD support, you can be sure of it as Linus uses it himself, he mentions it in his blog. (he is using an intel SSD drive) http://torvalds-family.blogspot.com/2008/10/so-i-got-one-of-new-intel-ssds.html [blogspot.com]
  • Awful article (Score:5, Insightful)

    by Nick Ives (317) on Thursday December 11 2008, @11:53AM (#26076617)

    It conflates the results of several independent tests to form the view that XP is somehow best. It also bandies about meaningless numbers like one OS being x% faster than another without giving any hint of the metric.

    Avoid.

  • by timeOday (582209) on Thursday December 11 2008, @11:53AM (#26076625)
    Filesystems are fundamentally engineered to cope with the high latency of hard drives, so I'd imagine there are a lot of assumptions to unlearn. But what other implications are there for the OS? Since the tradeoffs between RAM and persistent storage are smaller with SSD, maybe the changes should go beyond the filesystem into the virutal memory system?
    • Re: (Score:2, Interesting)

      by MattBD (1157291)
      Isn't LogFS designed specifically for flash memory? At present most flash drives seem to come with FAT, purely because anything can read that, but that's sure as hell not designed for flash. Seeing as portable music players seem to be heading towards using flash memory, they could do with something like that.
    • by SanityInAnarchy (655584) <ninja@slaphack.com> on Thursday December 11 2008, @12:53PM (#26077601) Journal

      Well, the article is crap in many ways -- doesn't cite what benchmarks they actually used, just throws around meaningless percentages and outright lies (Linux and Win2k absolutely do run things in the background).

      One of the other little details they left out is which filesystem they used, on any platform. My guess is, they just used the default -- I wonder if they were even aware of alternatives (you can install Win2k on FAT32, if you really want).

      So, to answer your comment, Linux has at least two filesystems that are designed to work directly on solid-state media. Unfortunately, most SSDs pretend to be ATA hard drives, but the point still stands -- Linux has many filesystems. I wonder which one actually performs best on that ATA drive?

          • by SanityInAnarchy (655584) <ninja@slaphack.com> on Thursday December 11 2008, @03:20PM (#26080213) Journal

            Bad analogy. This is a totally different issue. Memory fragmentation means you leave little gaps in the allocated blocks which are too small to reuse, effectively wasting memory.

            Given a sufficient number of small files, this can happen with filesystems, too. Of course, it's usually not as pronounced, as most filesystems won't pack more than one file into a block...

            Keep in mind, the block leveling algorithm will be abstracting the actual disk organization; defragmenting wouldn't accomplish anything on an SSD

            It would, at the very least, consolidate extents.

            I would also say, it's sad that SSDs have block leveling in hardware -- I mostly blame Windows for that.

  • ...a lost opportunity... Since the market has already hit its peak and it's too late now. And they'll never be able to sell to the 20 people that are using SSDs.
  • Summary FAIL (Score:4, Interesting)

    by Wonko the Sane (25252) * <wts42@yahoo.com> on Thursday December 11 2008, @11:58AM (#26076703) Homepage Journal

    "If you really want to go inside [the OS numbers], Windows 98 was the fastest of all," Far said.

  • by Viol8 (599362) on Thursday December 11 2008, @11:59AM (#26076727)

    FTA:

    "Linux is "always faster" than Vista or Mac OS X -- to the tune of 1% to 2% -- because like Windows 2000, "it never runs anything in the background."

    I'm sorry , what? Have these people never heard of daemon processes? What the hell are they talking about?
    If this is their level of expertise I think I'd take any tests they do with a whole cellar full of salt.

    • by Shados (741919)

      They meant relevent things. For example, XP will defrag your disk without you asking it to as soon as you're marginally idle... Vista the same, but will also index your disk continually...

    • Re: (Score:3, Funny)

      by deek (22697)

      You must have missed the change. It was a major feature for the Linux 2.6 kernel series. All linux processes now run in the foreground. Running a process in the foreground saves on overhead, thus resulting in a significant improvement in speed. Easily more than the 1-2% that the article mentions. I suspect the article downplayed the speed advantage, to cast Windows in a better light.

      Linux achieves this ability by forking the process from the shell, and redirecting the inputs and outputs away, thus givi

  • Uhm, what are they talking about? What are the things "running in the background" that are presumably hitting the disk all the time? Why do they believe that Windows 98 somehow magically bypass the wear-levelling built in to the SSDs? Or are they talking about raw flash, not sitting behind a controller?

    I find this a little scary too: Microsoft also plans a certification program for SSDs

    The conspiracy theorist in me see a future with proprietary extensions and requirement for getting certification is to ma

    • by James McP (3700) on Thursday December 11 2008, @12:13PM (#26076955)
      I find this a little scary too: Microsoft also plans a certification program for SSDs

      TFA: "Microsoft also plans a certification program for SSDs so that the drives properly identify themselves to Windows 7 and prioritize data I/O for the SATA interface. "

      While MS is known for embrace-extend-engulf, this is nothing to panic over. If the drive passes a string that identifies it as an SSD, Win7 (or any other OS) will use different disk control logic than they will for an HDD. All OSes will benefit if there's a clear way of identifying SSDs; MS, Linux, Apple, Sun, IBM, all of 'em. Change the preferred block size, alter garbage management, adjust caching to deal with 1 ms response times, (typically) fast reads,(typically) slow writes, etc.

  • Stupid article... (Score:5, Interesting)

    by Cyberax (705495) on Thursday December 11 2008, @11:59AM (#26076741)

    Have they tuned Linux for SSD? Like setting no-op IO scheduler (which gives about 20% speedup on some workloads)?

    I suspect that Win2000 and Win98 win because they have the most simple (and stupid) IO schedulers. That's a problem for conventional HDDs, but it's an advantage for SSDs.

    Also, they are talking about "Win98 doesn't support wear-levelling technology". But that's incredibly stupid since modern 'disk-like' SSDs do wear-leveling in hardware.

  • by The Man (684) on Thursday December 11 2008, @12:00PM (#26076749) Homepage

    Since they didn't test Solaris, the test is meaningless. It's the only OS in existence right now with caching and data management features designed specifically to take advantage of flash to improve real-world performance. The submitter's assertion to the contrary is a deliberate lie, an assumption that until Microsoft does something it hasn't been done, or at best sheer ignorance.

    Read up on the ZFS L2ARC and the use of supercap/DRAM/flash subsystems for separate intent logs that make up the hybrid storage pool [acmqueue.org]. There are plenty of white papers and other material out there, and of course you can also read the source code. [opensolaris.org]

      • by nvrrobx (71970) on Thursday December 11 2008, @12:35PM (#26077265) Homepage

        With all due respect, I call shenanigans on your logic here. OpenSolaris is just as much of a desktop OS as Linux is. Have you looked at the hardware it supports and what runs on it recently?

        The word "desktop" isn't even mentioned in the article anywhere.

        After reading TFA, it all feels a bit vague anyhow. I see no real performance results, just a few percentages thrown around.

  • by francium de neobie (590783) on Thursday December 11 2008, @12:01PM (#26076771) Homepage
    When I read into the middle, it says,

    According to Far, Mac OS X runs "a little faster than Vista" with an SSD drive, but Linux is "always faster" than Vista or Mac OS X -- to the tune of 1% to 2% -- because like Windows 2000, "it never runs anything in the background."

    Ok, so Linux and Windows 2000 never run anything in the background. My head exploded so I stopped reading.

  • The article is all over the map, discussing in vague terms everything from boot-up speed to I/O speed to some sort of generic "runs a little faster" that I assume (?) means overall system or app benchmark performance.

    When actual numbers are quoted, they sound somewhere between questionable and boring. The article quotes all sorts of differences in the range of 1% and 2%. Leaving aside the question of what this is a 2% difference in, and whether a difference that small is even consistently measurable outside of sampling error and quirks of their particular setup, does it actually matter? I'm certainly not going to choose an OS based on a 2% difference in SSD performance.

  • A lot of the really small low power laptops use SSD hard drives. Dell's mini's use them. There is a market for these little laptops. Granted these are not for gamers, or engineers. But for email, web surfing, taking notes in class, these things work fine. I have seen a lot of those Dell mini's in the hands of college students. This fall I may see a lot more.

  • Why would I care? (Score:5, Insightful)

    by Trillan (597339) on Thursday December 11 2008, @12:10PM (#26076891) Homepage Journal

    Even if their methodology was clear.
    Even if their methodology was valid.
    Even if every percentage point was accurate.
    Even if all of their arguments were valid.
    (And none of these are true.)
    Why would I care enough about 5% to let that pick my OS?

  • by CannonballHead (842625) on Thursday December 11 2008, @12:13PM (#26076945)

    It's not only 'bad' it's weirdly bad.

    According to Far, Mac OS X runs "a little faster than Vista" with an SSD drive, but Linux is "always faster" than Vista or Mac OS X -- to the tune of 1% to 2% -- because like Windows 2000, "it never runs anything in the background."

    Never runs anything in the background? What in the world does that mean? Am I missing something, here, or is this just the wrong terminology to use? Even at the most basic use level, you can "background" an application in Linux with the ampersand ... I'm confused.

    Not to mention that they didn't test Linux... or, presumably, any Unix OS. They basically only tested Apple and Microsoft operating systems. Hm. I actually like Windows on occasion, and I find that pretty stupid. (I also like Linux :) )

    It did have some interesting things to say though, like the block alignment.

  • by NineNine (235196) on Thursday December 11 2008, @12:14PM (#26076963) Homepage

    Obviously, SSD's are in their infancy. NO OS has been even remotely optimized for them yet, I'm sure (except maybe the big hitters, like Solaris). I'd be willing to be my left leg that the next version of every commercial OS (OSX, Windows, Linux*) is optimized for them. This article is irrelevant.

  • Wasn't a massive test. Used Swingbench against 170g database. Quad core, 2gig. Disks were 300g 15k fiber, dual pathed. Swingbench seemed to be like 50 users running VERY poor queries, so this was almost 98% reads. Ms response time was between 3-4, cache hits minimal. Added EMC (1) 146g SSD into the disk group. Response time hit .4 to 1 ms response, identical tests.
  • by flajann (658201) <flajann@NospAm.linuxbloke.com> on Thursday December 11 2008, @12:19PM (#26077053) Homepage Journal
    This article fails in several respects:
    1. Linux, a very major OS, is not even included in their tests.
    2. A proper test would not have ANYTHING running in the background.
    3. Issues such as how much read and write caching the OS does will affect performance.
    4. Article does not list a performance table or chart -- but perhaps I missed that.
    5. The actual File System used is really at issue here, but the article did not mention anything about File Systems from what I could tell.
    6. Defragging a SSD? Shouldn't need that. And obviously defragging schemes which were written for magnetic hard drives will probably be less than optimal for the SSD anyway.
    7. Article, as far as I could tell, did not cite the benchmarking methodology used.

    Overall, I would state that this article is useless beyond "cocktail gossip." And really, SSD should have a specific FS written to its peculiarities, which would, of course, render the "OS" questions moot.

      • Linux is not a "very major OS" [...] that has less than a few percent of the desktop market

        Who said anything about the desktop market? There are plenty of subnotebooks, handhelds, and embedded devices that boot from flash into a Linux-based environment. I would imagine that even servers could benefit from the faster seeks and lower heat dissipation of SSDs for some workloads.

  • by zealot (14660) <xzealot54x@NOspam.yahoo.com> on Thursday December 11 2008, @01:35PM (#26078325)

    >I'm suspicious of the suggestion that a log-based
    >filesystem will cure all the ills of the limited flash-
    >controller based wear leveling.

    Yeah. Total bull.

    Anybody who thinks the filesystem can do really well has
    bought into the crud from most existing vendors about how
    you have to use those things differently. If you really
    do believe that, you shouldn't touch an SSD with a ten-foot
    pole.

    If the flash vendor talks about "limits" in the wear
    levelling, and how you have to write certain ways, just
    start running away. Don't walk. Run away as fast as you
    can.

    >A question keeps coming up in my mind about what happens
    >when you split an SSD into multiple partitions, and what
    >*you want to happen*. I use separate partitions for root,
    >boot, and var, because I tend to make root and boot
    >read-only.

    Again, if your SSD vendor says "align to 64kB boundaries"
    or anything like that, you really should tell them to go
    away, and you should do what Val said - just get a real
    disk instead. Let them peddle their crap to people who are
    stupider than you, but don't buy their SSD.

    So what you want to happen if you split an SSD into multiple
    partitions is exactly nothing. It shouldn't matter
    one whit. If it does, the SSD is not worth buying. If it is
    so sensitive to access patterns that you can't reasonably
    write your data where you want to, just say "No, thank you".

    Anyway, I have a good SSD now, so I can actually
    give some data:
    - Most flash-based SSD's currently suck.

    I don't have these ones myself, but last week we had the
    yearly kernel summit here in Portland, and a flash
    company that shall remain nameless (but is one of the
    absolute biggest and most recognizable names in flash)
    was selling their snake-oil about how you need to write
    in certain patterns.

    So I called them on it, and called them idiots. Probably
    one reason why I didn't get one of the drives they were
    handing out, but one of the people who did get a drive
    was the Linux block system maintainer. So he ran some
    benchmarks.

    Those things suck. You will never get any decent
    performance of anything but a very specialized filesystem
    out of them, unless you use them as essentially read-only
    devices.

    For a basic 4kB blocksize random write test, the SSD got
    around 10 IOps. That's ten, as in "How many fingers do
    you have?" or as in "That's really pathetic". It means
    that you cannot actually use it as a disk at all, and
    you need some special filesystem to make it worthwhile,
    and certainly means that wear levelling is probably not
    working right.

    (For the math-challenged, 10 IOps at a 4kB blocksize
    means 40kB/s throughput and 100ms+ latencies for those
    things. It also means that even if some operations are
    fast, you can never trust the drive)

    - In contrast, the Intel SSD's are performing exactly as
    advertised.

    I did get one of these, with warnings about how
    if I want to get low-power operation etc I need to make
    sure that disk-initiated power management is enabled etc.

    Whatever. The important thing is that the Intel SSD does
    not care one whit where you write stuff, or how you do
    it. With the same 4kB random write b

  • by calc (1463) on Thursday December 11 2008, @01:59PM (#26078751)

    I am at the Ubuntu Developer Summit at Google and listened to a talk given by tytso a few days ago. He mentioned that both ext4 and btrfs will support a new ATA command to tell the drive that a particular sector in no longer in use so that it can reuse it for better wear leveling. So it appears Linux will have better support for SSDs in the near future.