Slashdot Mirror
Which OS Performs Best With SSDs?
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."
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?
If I have nothing to hide, don't search me
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.
Nick
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?
What is your criteria for a different file system? NTFS is already a very good one for most of the important criteria.
from TFA: "Linux is "always faster" than Vista or Mac OS X"
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.
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.
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
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?
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.
I've been on slashdot so long I'm starting to get out of touch with the cool stuff if it ain't on slashdot.
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.
the source of windows 2000 was leaked a few years ago. http://www.kuro5hin.org/story/2004/2/15/71552/7795
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.
Ruby Neural Evolution of Augmenting Topologies
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.
All hope abandon ye who enter here.
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 going to be much of a performance difference. If they are frequently accessed, then the difference would be huge. I've seen desktops that topped out at 30% fragmentation. The performance after dragging is night and day. Its much more important for me to have consistent performance ( due to automatic reallocation of files when they would be fragmented) than a gradual slowdown that requires downtime for defragmentation.
Note, haven't run windows in production servers for the past ten years. But I don't think NTFS has changed that much since then.
Well.. maybe. Or Maybe not. But Definitely not sort of.
I hate to say it, but Apple OS X IS a Unix OS...
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.
I think you mean "head", not "needle", unless we're talking about 33 RPM vinyl discs here.
Gamingmuseum.com: Give your 3D accelerator a rest.
The point of the article is that solid state drives have different performance characteristics than hard disks. Since SSDs are random-access devices, fragmentation does not increase seek time. Therefore, it makes sense that a filesystem that doesn't try to worry about fragmentation could perform better on SSDs.