Software developer’s PC’s really just need lots more RAM than the other, standard issue, office desktops right? After all, it is the accepted and cheapest way to give a machine a power boost – add more RAM.
For a minute, imagine a small office building with a large car park and that the most efficient way to give the same instructions, to as many employees as possible, is to have the employees assemble outside and the boss stand in the car park with a megaphone.
Now picture that small office block as an analogy of a typical office desktop PC:
- The people spread throughout the building represent – blocks of data on a hard drive
- The elevator represents – the hard drive head
- The space in the car park represents – the RAM
- “The boss” with the megaphone – you guessed it, the processor
Right, so back to our first sentence, more RAM equals bigger car park. “The boss” can address more people at once in his new supersize car park, or just keep groups of people nearby, ready to receive instructions because there’s plenty space for everyone.
That scenario is all very good when we’re dealing with databases and we want to process bigger chunks of data and have lots of data ready, on standby, to be accessed quickly. And lots of developers run databases on their local machines, so we want lots of RAM for this.
BUT, we’re forgetting something that developers will probably do more frequently than anything else – compile stuff! Compiling is a more granular operation that is done over lots of small blocks of data and involves lots of reading / writing at the same time. Using our analogy above, you might picture that the size of the car park becomes partly redundant for this bit – we need to address lots of small groups of people and send them back and forth between the car park and their offices. And it’s the elevator, aka hard drive, that’s going to be doing most of the work for this bit. It doesn’t matter how big your office block is (large hard drive), or how much space you have in your car park (amount of RAM). Compiling is more about how fast you can get people between the car park and their offices, e.g. read and write data to different parts of the hard disk.
So by this point we’re already agreed that we’re keeping our RAM upgrade, we need it and we’re not giving it back! BUT we’ve realised that we also want a very fast hard drive.
Now, how many of you developers out there have a faster hard drive than, lets say, the office administrator or than Mr top sales guy from the Sales department?
If you answered “no” to the question above, start watching how many cumulative minutes a day you spend waiting for your hard drive to finish some operation. Paying a small premium for a faster hard drive, such as the Western Digital VelociRaptor might pay itself back several times over in time-savings. Developers don’t use their workstations in the same way as everyone else – every core component should be upgraded to balance the system. More on how to convince “The boss” that you need an upgrade in a following post, shortly.
Ok for desktop, but much harder to put a very fast hard disk in a laptop. Ram upgrade are always good, as they take very little time, and does not stop the programmer working while setting a machine up again.
Readyboost is also easy and quick to install and helps a bit with disk access, so might was well use Readyboost.