Solid State Drives - Fast, Rugged, and Expensive 215
Nick Breen writes "Are solid state drives becoming a reality? Loyd Case over at ExtremeTech has written an article concerning the current state of SSD with a comparison between a Samsung 64GB SATA and a Super Talent 32GB SATA. While they showed impressive speed rates when placed against a hard disk drive, the occasional sporadic statistic (and high cost) indicate they're not quite ready for the mainstream. Dell and Alienware have been shipping laptops with SSDs for months now, and Apple may be rolling out one of their own next year. Is the time of the solid-state drive almost at hand? Does anyone have any first-hand, practical experience with SSD?"
Re:you left impractical off the list (Score:3, Insightful)
SSD's have a short life span due to cell memory, and they aren't immune to shocks damaging them. laptop hd's will take all kinds of poundings, only a direct solid hit during a r/w would possibly damage them
Re:Where is this applicable? (Score:4, Insightful)
Hopefully an outlier (Score:2, Insightful)
Re:Where is this applicable? (Score:5, Insightful)
Actually, if you do any sort of multitasking, you'll probably notice it's a lot "snappier" (apps load faster, switching apps doesn't seem to take so long, etc). Or if you're a typical home user with decent RAM but still have all the usual crapware loaded, WIndows won't feel so slow. Or you don't defragment your disks and let your disk get horribly fragmented...
The deal with SSDs is that they can manage their peak datarates all the time. With disks, the smaller the I/O transfer, the slower the disk becomes. If you have a disk with a 5ms seek time, you're limited to 20 I/Os per second. If you read maybe 16 sectors each (8kiB), it means your disk throughput is on the order of... 160kiB/sec. Seeks are taking a lot of time compared to the actual time it takes to read the disk.
An SSD has negligible seek time, so reading those 160kiB off an SSD won't take noticably longer than reading 160kiB in one read (the overhead of doing the transaction over the ATA bus is the biggest overhead).
You won't use an SSD if you need high throughput, where you're basically doing huge writes or huge reads (i.e., media center media disks, video capture/production, etc). But a home user that's doing a lot of little random I/O will notice that the entire system feels "snappier" as the I/O is mostly seek-bound, not throughput-bound (small I/O). This applies as time goes on as most people don't defragment their disks (you don't have to, or should, with an SSD, since wear-levelling may still not put it contiguously on the flash media), so even a heavily fragmented disk will still feel fast with an SSD.
Re:Mods, Bad Mods, and Current Moderators (Score:0, Insightful)
Give me RAM (Score:3, Insightful)
I've been using Flash longer than most... From wiring minuscule capacity EEPROMs into embedded circuits, to squeezing OSes down to 8MBs for firewalls. Floppies are a no-go for important systems.
They're low power, quiet, and have high speed seeking, but I don't really care. What I want most in a drive is seriously high throughput... That probably means RAM, with a battery back-up. In the mean time, HDDs keep getting faster and quieter.
I have an EEE with a solid state disk drive (Score:4, Insightful)
Re:And, the MTBF is.. (Score:5, Insightful)
Puppy Linux (Score:3, Insightful)
Re:Where is this applicable? (Score:3, Insightful)