I have a MacBook with 8GB of RAM and a 500GB 7200rpm hard drive. I write software for a living. I am contemplating getting an SSD Drive, but I am unsure about the performance.

Do SSD drives really make a nice speed difference?

7 Answers 7


From what I've experienced - YES. They are definitely worth the price for blazingly fast read speed during a large project compile.

  • My friend bought one for his Windows laptop and it made a huge difference to development speed. Note though that prices will fall rapidly and performance/capacity will increase rapidly.
    – Eric J.
    Jan 28, 2010 at 21:27

If you are like me and you are constantly opening and closing apps, specially apps like IDEs with large projects you will quickly benefit from the performance of an SSD. I just bought a Sandforce-based SSD (285mB/s read and 275mB/s write) and I'm really enjoying it. MacOSX boots in under 20sec and native apps open instantly, including Mail.app and other crappy software like Photoshop or Word. Git is faster checking out branches and well... everything feels faster.

If you are getting one just make sure you get one with a Sandforce controller. They specially work better on OSX (due OSX does not support TRIM and have garbage collector).


I am also a software developer and I recently added an ExpressCard SSD as the boot drive in my MacBook Pro. It has improved the performance of everything.


Short answer - it's worth it.

Long answer - I'm a software developer who has a SSD in every machine, and yes, it's worth it because it makes your machine much more responsive.

Your compile times probably won't decrease, however, as that's almost always a CPU-bound process and not a disk-bound process.

You may be thinking, "But doesn't my build process involve a zillion small files? Isn't that where SSDs shine?"

A modern OS like OSX is pretty smart about caching small, frequently-used files in memory. If you're accessing the same small files over and over (a typical pattern when you're dealing with eg. a large software project) these will be pretty efficiently cached into memory by the OS. This, combined with the CPU-intensive nature of compilation, is why compile times are typically not limited by disk speed.


It's difficult to say exactly how an SSD may be of benefit specifically for software development, without more details of the typical tasks you do (e.g., databases, writing web applications, compiling a large codebase, etc.). If your particular bottleneck is the CPU, then an SSD may yield little improvement.

But I would strongly recommend SSDs based on the overall improvement to performance that comes from the incredibly fast random read/write speeds (as well as the fast sequential speeds), which may itself make your life easier as a developer. Booting, launching applications, using a web browser, etc., are all noticably faster.

There is also a similar question here.


They allow for faster read/write to disc than the average home hard disk, however, you should be writing software to run on your expected audiences hardware, not your own. Don't write an application that runs perfect on your machine, but may not run so well on other machines.

That said, there's not much difference programming-wise for developers. The only situation where it will get you a good difference is when doing a lot of read/write operations on disk.

One more benefit to a SSD, for you, since you have a MacBook, is it should extend your battery life, as it draws less power than a traditional disk/platter HDD.

  • 7
    I have to disagree with your first paragraph. Development environment often has significant overhead on resources; also users do not experience long compile times like coders. Therefore it is vital for programmers to use powerful machines for writing code. Testing code is another task, and this should already be done in different environments on different machines -- some of them with SSD, some of them without.
    – liori
    Jan 28, 2010 at 23:53
  • Debug code and release code are very different. In one 3D application I'm writing, my maximum FPS doubles in the release build versus the debugging build. Sep 6, 2011 at 15:13

Here are benchmarks for one in particular: http://www.slashgear.com/samsung-64gb-ssd-performance-benchmarks-278717/ The rest are similar

Unlike normal harddrives, higher capacity SSDs typically have lower R/W speeds. Higher capacity also is more expensive.

As a software developer, you need lots of space, too. Up to you what you think is worth it. The WD velociraptors might be a nice alternative. Or if money is no object, go SCSI

  • SCSI with his MacBook?
    – Chris_K
    Jan 28, 2010 at 21:40
  • 3
    I have to disagree; SSDs tend to be faster the larger the capacity (anandtech.com/storage/showdoc.aspx?i=3631&p=27). The drive is able to use any extra free space to help de-fragment itself: anandtech.com/storage/showdoc.aspx?i=3631&p=8
    – sblair
    Jan 29, 2010 at 0:57
  • 1
    Also larger capacity SSDs often put more flash memory chips in parallel, sort of like going from a 32-bit-wide bus to 64-bit-wide bus: You get twice the data in the same amount of time. So go large! (Then sell you car to pay for it!) Oct 28, 2010 at 1:26
  • Hey guys, when I answered this in January this was not the case with the drives available at the time. Oct 28, 2010 at 20:02