Toshiba Begins Selling MacBook Air SSD
Lucas123 writes "Toshiba has made the solid state drive used in the new MacBook Air generally available for use by equipment manufacturers. At just 2.2mm thick, the company said the drive represents a new form factor that is about one-third the thickness of a thin hard disk drive and that is 42% smaller than even a mini-SATA SSD module. The new Blade X-gale SSD series has a maximum throughput of 220MB/sec. and can store up to 256GB of data."
so with this tiny form factor, is there any way to install this inside a unibody macbook pro? I'd love to go SSD but want to keep a spinning drive for decent storage capacity, and don't want to lose my dvd drive.
come on OWC, make it happen! :)
dave
I've been pricing out a new laptop, and I've love to get one with SSDs, but DAMN they're expensive.
You should price out what an original IBM PC cost. You were looking at $1500 starting price, and that didn't include any kind of floppy or hard disk, and 64K (not M) of RAM. What you paid back then for two floppy drives would probably buy you a decent laptop nowadays. Hard drives started at $10 per M, and 30M was a large drive (in both physical size and storage capacity).
And you had to walk 30 miles uphill (both ways), in the snow, to get to/from school.
Who would win this election: Andrew Weiner vs Andrew Weiner's weiner.
Not donwplaying your need for adequate storage, but SSDs cope with running near-full MUCH better than HDDs, since fragmentation is a non-issue.
Like much common knowledge, this isn't accurate.
You don't suffer from one aspect of fragmentation -- the heads don't have to move and the disk spin into a new position.
However, you do still suffer from excessive continuation blocks on a fragmented drive, with both loss of space and a slight loss of speed as a result.
But even worse, for an SSD is another factor: There's a fixed amount of write cycles per block.
As a disk gets near full, this causes two problems:
TRIM helps with the second problem in that you tell the drive which blocks are really free so it can reshuffle and pre-erase sectors in idle time,
but the effectiveness of TRIM goes down as the disk fills up (there are fewer sectors that can be pre-erased), and on a nearly full disk, it only takes a few minutes of high activity to make the background garbage collection not being able to keep up, and you get serious stuttering as a result. Strange as it may seem, the worst case random write access is far higher for an SSD than for a HDD, and that's where you'll feel the pain as a disk gets close to full.
In fact, it's recommended to leave parts of an SSD unpartitioned to give the wear leveling and garbage collecting routines more space to work with. ("Good" drives already have 20% or more set aside for a combination of wear leveling, garbage collection and bad block mapping, but the current crop of consumer drives only have around 5-7%, and really need more, especially as the drives mature and bad blocks have to be remapped.)
So no, you shouldn't fill an SSD - at least not if you use it for random write. If you use it for store-once-read-many, it doesn't matter much, but a 98% full OS SSD drive is going to hurt -- bad.