Now that I've got an SSD as a boot drive, navigating the Finder is significantly faster. It feels so quick. Folders open instantly. When I got my development environment up and running (nginx, uwsgi, django, mysql, etc...) I noticed that code compiles wayyy quicker too.
Love it! For the record... I've got the Intel X-25M, second generation. It's only 80GB (they're pricey!) so I also picked up an MCE Optibay which is basically a hollowed out superdrive that lets you mount an additional HD where your DVD drive sits. It also includes an external enclosure so that you can put your otherwise useless SATA DVD drive to use via USB. So now my MBP has two drives in it, an 80gb ssd to boot off of and a 320gb regular drive for bulk storage (media, photos, etc..)
Gotta give credit where credit is due... Paul Stamatiou's blog came in handy a few times with aiming me in the right direction with this. Here is a nifty article from his blog, which describes most of what I did other than the RAID part (which I did not do). http://paulstamatiou.com/how-to-apple-macbook-pro-raid-0-arr...
The downside is that sequential writes are bandwidth-limited compared to other SSDs, but this doesn't matter in practice with small random writes completing very quickly.
As I noted in that article though - SSD RAID 0 on a Mac is a danger zone because there's no TRIM. My first single, non-raid SSD (X25-M G1) died after 9 months of typical development usage. So I backup like a banshee. The speed boost is worth the risk though.
Say you have an SSD that consists of 8x16GB chips. Internally it's implemented in something like a RAID0 array, which is why they're so fast. If the capacity doubles / size shrinks by a factor of 2 and someone decides to stick 16x16GB chips in the next gen SSD then you will see a speed increase. On the other hand if they go for 8x32GB you won't.
My comment was directed to Matt_Cutts' complaint that he didn't know when to buy an SSD. I don't think it matters exactly when you buy one. (Though I personally am waiting to see how Intel's 25nm SSDs compare to those based on the SandForce SF-2000 controller around Jan/Feb 2011. Maybe I should practice what I preach.)
This may be because I have a lot of ram, because I mostly work with small files, or because I'm using Linux which seems to be more resistant to bad disk IO speeds.
However I do like the gain in battery life.
The most interesting insight I can offer is that because there is no seek time penalty and SSD throughput increases as the I/O scatters, our tests with RAID 5 are essentially as fast as RAID 10, which makes $/gb much better than it looks at first blush.
TRIM through hardware RAID is still an unsolved problem for us, as is getting wear life SMART data (Intel X25M G2) through the RAID controller. My gut feeling is that the final solution is probably a JBOD controller and Linux software RAID.
I saved the results from tiobench from some of my initial testing with 6 intel x-25m here: http://gist.github.com/348417
Not bad for $2400 worth of ssds.
On thing I noticed with the X-25M G2s is that if you are in a write intensive environment they will degrade in performance dramatically. The SandForce SF1200/1500 drives seems to handle garbage collection much better and run with lower write amplification levels. I've found that the SandForce drives do a much better job at maintaining acceptable random write performance after months of being beat on. That all being said a beat to hell X25-M is still 10 times better than a spinning disk.
If you want I can run an iometer batch or figure out tiobench if you'd like some runs on the 9211 or 9260 to compare with your ICH and Adaptec runs. Ping me at gomeler at gmail if you are interested.
On a more personal note I use a Seagate Momentus XT in my Macbook Pro and this is the single best investment I made in years! This thing cost a third of a "real" SSD of the same capacity and for what an SSD is shining (boot time, application launch, ...) it's on par. The 4GB SSD cache is really improving the experience (they should offer an 8GB version though).
I can't recommend this enough if an SSD is too expensive or not capacious enough.
If you have a laptop as your primary machine and need to store music and photos, SSDs with sufficient capacity are prohibitively expensive, which is where hybrid drives are ideal.
The one thing that's given me hesitation with regard to it, is the reliability problems Seagate was running into a while back, e.g. the "click of death" (very) premature failures on some of their 1 GB drives.
If anyone has appropriate experience/observations, has their reliability trended back towards its old, high levels?
One word of caution though, when the SSD runs out of free blocks and has to re-use blocks marked as deleted, the performance hit can be pretty painful ... sudden application freezes that take many seconds to resolve are not uncommon (This is from Windows XP ... I spend a lot of time in it on my Apple machine)
There is a TRIM command that is supposed to help with this problem http://en.wikipedia.org/wiki/TRIM, but only Windows 7 and Linux support it at present.
As for "sudden application freezes" on XP. That's not true unless it's true for all people running XP. My systems NEVER freeze on HD, or SSD. But WAIT. I see what you are doing. You run in IN your Apple machine which proves my point that Apple Mac's are cheap hardware, and also the drive is not formatted in regular NTFS which also helps to slow it down. Don't sit there on a slow mac thinking how slow XP is. Get a high end PC for under $1000, and watch it out do your mac. Also notice how mac doesn't support TRIM.
But again. I see one of you Macbook Pro users about every 2 hours. Please don't tell me you bought it because it was faster and better. It's not. Only in terms of the fact that it's so obscure that you are less likely to get malware. But it's not a big enough difference to matter really. Other than this one point, there is NOTHING better about mac. Unless in a stylistic way, you like the shiny colors etc. The OS's are far too similar and both work just fine.
If your laptop is your profession then you care about the tools you use, you're right it's not down to speed, it's down to the thought that goes into every element of both the hardware design and user interface that means my computer thinks along the same lines as me.
The cost extra is minimal when you offset it across 2-3 years of earning but the difference it makes in small increments to your daily working life is more than worth it.
It won't make purely random reads fast, but it makes my workloads scream.
Also, you don't need to sweat the higher price per byte, because more and more of my files (and I would assume yours?) are on the cloud every day anyways, so 256GB or even 128GB is fine for me these days.
For me, media files were a killer too, so I simply put my media collection on an external HDD, "cached" my favorite 20GB or so of content on my SSD (the stuff I put on my iPhone, essentially), and started relying more on streaming services like Pandora, Rdio, and Hulu, etc.
I did this in July and I haven't used the external drive even once...
Works great, and we do heavy queries at lightning speed. We currently run Ubuntu Linux on it but would switch to FreeBSD 8.x if the Java support was better.
Since OS X lacks TRIM support (arggh!), normal SSDs tend to degrade in performance over time. The OWC's are designed with a microcontroller to do the equivalent of TRIM behind the scenes, and they also happen to be fast as hell. I upgraded from a year-old 64g Kingston to a 120g OWC, and the speed boost was just as noticable as the original move from a spinny drive to SSD. (Down to a 22 second boot time on 3yo hardware!)
Doesn't TRIM necessarily rely on knowing which blocks contain live data and which contain deleted data? I.e., something the hardware can't know?
Most people confuse trim with garbage collection, which proactively cleans out invalid data (creating more pre-erased blocks to speed future writes) and potentially defragments data (to speed future sequential reads).
I switched to a 120GB OWC Mercury Pro SSD in my MacBook Pro.
The upgrade is impressive enough that I understand why some people end up ditching the optical drive entirely in their MacBook Pros.
I honestly would not be surprised if we don't see the MacBook Pros lose the optical drive entirely in the next year or two. Steve is notorious for dumping dead technologies when the time is right and the CD/DVD is one of those. I haven't put a CD in my laptop since I bought it and the only time I ever use a DVD is to boot into the startup disk or watch a movie.
The best decision that Apple could make at this point is to offer a MacBook Pro with either two SSDs, possibly in a RAID 1 configuration. Speed and security of data is now more valuable to the average consumer than the convenience of being able to read DVDs and CDs.
The alternative would be to sell MacPros with one 60-120GB SSD drive to boot off and run applications from and a conventional HDD with 320GB+ to store stuff like photos, video and music on.
If you are debating an upgrade to SSD, don't. Just buy one already.
* Cold boot (Power button to login screen): 79s HDD, 76s SSD (didn't improve much, surprisingly)
* Login (Login -> Desktop menu bars loaded): 16s HDD, 6s SSD
* Firefox start: 11s HDD, 3s SSD
* OpenOffice start: 11s HDD, 3s SSD
* Metasploit msfconsole start (i.e. loading lots of ruby code): 22s HDD, 12s real
A lot of other things are noticeably faster. Searching for things in Spotlight is almost instantaneous. Previously, there could be a few seconds delay between typing a filename and seeing it appear in the results. Running find over large directories is noticeably faster as well. Time Machine backups are way faster, since it takes much less time to determine what has changed since the last backup.
I was a little hesitant to get an SSD knowing that OSX doesn't have TRIM. We'll see how it goes. I'm hoping Apple adds support soon. If not, I might be doing a secure erase and re-install periodically.
For me, multi-tasking is the killer feature: being able to load up Visual Studio, Fireworks and anything else I fancy at the same time without having any noticeable impact on system performance has made me really fall in love with my SSD.
Like many I've come to accept that SSD's will be roughly $2-3/GB for a while to come. I'd hate to spend all that time waiting while my spinny drive churns away valuable seconds of my workday.
We're currently stuck with PCIe->SATA controller->SATA attached NAND controller devices that implement their own wear leveling and bad-block management with degree of effectiveness widely varying among manufacturer's implementations. We have to use post-hoc benchmark results to attempt to reverse-engineer the the performance/price/longevity tradeoffs that were baked into the device.
I suspect that no mass-market ASIC company will be willing to get this on the market until Microsoft ships an OS with a native NAND controller driver and flash-aware filesystem and a system OEM contracts with their BIOS vendor to allow booting from the thing.
http://stackoverflow.com/questions/499889/ssd-and-programmin...
its mentioned that CPU is by and large the bottleneck but over here:
http://javamoods.blogspot.com/2010/04/hdd-ssd-battle.html
the author mentions that the SSD gives big speedups to compile time.
Anyone has any data to share in regards to this?
When you compile, does your computer's hard drive thrash, or is the CPU pegged at 100%?
I'll answer "in production" with the caveat that important data should never be stored on ANY single disk or in any single location. (You'd think that would be obvious, but unfortunately, it's not, or else hard drive recovery services wouldn't do such a great business.)
I'm quite happy with the SSD in my laptop. I don't get any better battery life, but it does make the laptop "feel" faster.
My netbook is the System76 Starling netbook, and my desktop is custom built. The netbook takes about 15 seconds from Off the the Web. The desktop takes about 10 seconds from Off to the Web.
Launching Eclipse takes about 3 seconds (on the deskop; never tried on the netbook). Everything is incredibly fast.
I did some tests on having my local repository on the SSD, but it wasn't substantially faster than my regular HDD, probably because working with it is sequential and heavily cached.
It will be nice when SSDs are price competitive enough to be the only storage in a desktop computer, if only for getting rid of the heat and the noise.
Really, it's the single best upgrade anyone can make to their machine. At work, I've got two in a Mac Mini and it smokes any other machine at tasks not tied to CPU - building projects, rendering to disk, everything. At home I've got two in a 13" MacBook Pro and it's like being in the future.
My wife used my computer the other day, and she was shocked at the performance, enough to comment about it. She doesn't normally talk about computers or relative performance in things. Her computer is a 2008 MBP with a 7200RPM drive and lots of RAM - not far from my machine, except for the SSD.
It's noticable in all sorts of things beyond startup times when you swap over to a SSD drive. Even something simple like browsers; browsers speed up because whatever they are using to store history and the currently open tabs for crash recovery doesn't have an i/o lag and so the interface becomes much more snappy and pleasant to use with a solid state drive. Should your app write such small things immediately, and slow down the UI for a fraction of a second, or cache the writes in memory a little longer for not-so-critical data and write at an opportune moment? Depends on the app, but people should be wary.
That said, I will echo everyone else who uses them and say it's the single best investment you can make in your machine. Especially with 40 gig drives around $100, even if that requires a bit of juggling when you fill it up and have to move some of your data from your OS drive to your legacy drives/backup solution.
There are MLC SSD's and SLC SSD's. The former being reasonably priced (think <1000$), and the latter costing in the neighborhood of 5-10k per drive.
MLC SSD's have a fixed write lifetime and will die or degrade after a certain number of writes. SLC SSD's have no such limits.
Cassandra for example has a very predictable write workload given our application, but other datastores (like an active write heavy mysql OLTP DB) would kill an MLC SSD very quickly.
We are using Cassandra to drive an API that must service thousands of requests a second but also with sub 100ms response times. Not a typical web use of Cassandra. Response times from hard disk just were not fast enough for our needs.
A new type of MLC is hitting the shelves now too. Enterprise MLC... supposed to be more resilient to the issues MLC ssd's have faced.
We are using OCZ Vertex.
[citation needed]
I have an elevation service, which has 600gb of binary files which are queried randomly. Since I have users from all over the world using the service at any one time, the heads on the drives must be flying all over the place. Perfect application for SSD's, even if they are poor at wear leveling, because it's a read-only application.
As far as database is concerned, I'll be holding off until I am sure I won't be screwed by the wear leveling. My database is currently sitting at 91% reads, but as we grow I can imagine that 9% writes can add up way quicker on the server than any amount of writes do on a persons desktop.
I am a total convert to SSDs as a result. Still using HDD for the OS and other things like mass storage. When the price point is better I'll move all the disks across.
Now it's CPU that's the bottle neck :P
But, it's just a hack to begin with and SSD is the patch. I don't have the time/option to find and hack out a better storage mechanism for that particular task. RRD makes little sense in this day and age, but it's what I'm stuck with due to time constraints.
I'm starting to cycle these SSDs into production, got a couple coming Real Soon Now as vm containers. DBs are next, I just need to decide if I'm going to use flashcache or buy enough to go raid.
Some blogs says that the "easy fix" for lack of TRIM is to just backup/reformat/restore your SSD every X months. Eeech
It's not perfect, but it is easy to configure and can make some difference without the reformatting hassle.
My recommendation: if you're going to use SSDs, jump in with both feet first. Budget SSDs are ok, mine nets a 7.0 on the Windows Experience Index. It's actually the only technical bottleneck in my system that has an i7, 8 gigs of RAM, GTX 480, etc..
If I were to build my PC all over again I would have invested in a real SSD instead of dilly dallying with a budget SSD boot drive.
Our Server team is selective with the drives due to cost and making sure the problem area would really benefit from that type of drive.
It is so fast and silent that I decided to give it another try and I have been using it for three months now.
I didn't try to recover the data but I think that in case of failure or damage it is more difficult to recover the info than from traditional disks.
I put these into the machine as soon as I got it so I can't really comment on how much of a difference it would have made if I had left the stock HDD in there instead. That said, disk bound operations (like computing audio waveforms) happen in the blink of an eye.
I've bought another one until my dealer does RMA in the hope that it's not a "generic" problem.
TL;DR
SSD break out of the sudden and usually everything is lost. Don't use a SSD without having backups on a daily basis!
That goes for hard disks just the same.
SSD die just out of the sudden without any warning.
The second one was pretty nasty because of course we only found out about that one when enough drives had failed that we couldn't recover any more, and as long as it worked it seemed to work perfect.
Of course there is no way to know how long that second one had been giving off warning signs, by the simple fact that several drives had failed it must have been dead a long time before we found out about it.
Lesson learned: after configuring a raid system test if your 'drive dead' signal actually reaches an operator.
When there are physical reads, the response time is awesomely fast. An IO is less than 1ms. For the drive included with my machine an IO was ~10ms.
It's response time (not throughput - as seen in many benchmarks) that makes you want an SSD on your desktop.
The difference is similar to dialup --> cable.
Intel's self-serve support's organized better than Kingston's, but neither offers a subscription to notify of firmware updates like Dell does.
Waiting for memristors! ;)
Also VPSes with SSDs would be nice for database servers.
Win7 boots in 10 sek. Firefox-4 is up and responding in a fraction of a second.
will never go back on that.
But for servers and any other kind of storage I will not get near it because of price.