SSD Questions - Using an SSD as your OS Boot Drive

RavenPanther

Honorable
Sep 2, 2013
33
0
10,530
Admittedly, I haven't really kept up-to-date on Solid State Drive news. The last I read about them, several years ago, they were faulty, unreliable, and expensive. But I'm building a new rig and from a bit of research I clearly see that they've come a long way.

So this leaves me with a few questions about SSDs:

Is it as beneficial to partition an SSD as it is/was with HDDs? With the old hard drives, partitioning one meant faster access/writing and better segregation of data; somewhat akin to having a multitude of smaller drives instead of one huge drive. Is this still beneficial to SSDs, or do they not suffer from the slight lag due to the absence of a head?

Using an SSD as your boot drive is clearly a great route to take, because of the obvious speed advantages over HDDs. But what ~exactly~ should you have on your SSD? For example, I'll be running Windows 7 Professional (64-bit). Should I get a 256 gig SSD and partition the ~40gigs of space needed just for the OS, leaving the other ~200gigs for programs? (Yes, I could and will easily need to fill close to that much space with programs, alone.) OR Should I purchase a 256gig SSD, leaving it unpartitioned but storing both my essential Windows OS on it, as well as my programs? OR Should I simply purchase a ~64gig SSD and avoid partitioning, using a second SSD for the programs?
In any scenario, a RAID 1+0 (or RAID 10) setup of four WD Velociraptor 500gig drives will be serving as storage for general files.

I've never purchased an SSD before. Would one format them prior to installation? How much space do you lose with SSDs? (For example a 500gig WD HDD I have installed in my laptop is actually only 465.76 gigs, a 1TB WD is only 931.39gigs)

Finally, just out of curiosity. Who is your preferred SSD manufacturer? It looks like Samsung leads the field, at least currently. Crucial also looks very highly-revered.

Thanks!
 
Solution
Is it as beneficial to partition an SSD as it is/was with HDDs?

No.

Using an SSD as your boot drive is clearly a great route to take, because of the obvious speed advantages over HDDs. But what ~exactly~ should you have on your SSD?


AS my C, I have a 128 Kingston.
Windows 8 Pro, and almost ALL applications. Lightroom, Paintshop Pro, Corel Video Studio, MS Office 2013 Pro, a crapload of utilities. Currently, takes up around 49GB.
Games live elsewhere.

I also have another 128 (it was on sale when I got it), used for working documents.

Movies and music live elsewhere.


Go with a 256GB, and use that for OS and applications. Don't partition.

USAFRet

Titan
Moderator
Is it as beneficial to partition an SSD as it is/was with HDDs?

No.

Using an SSD as your boot drive is clearly a great route to take, because of the obvious speed advantages over HDDs. But what ~exactly~ should you have on your SSD?


AS my C, I have a 128 Kingston.
Windows 8 Pro, and almost ALL applications. Lightroom, Paintshop Pro, Corel Video Studio, MS Office 2013 Pro, a crapload of utilities. Currently, takes up around 49GB.
Games live elsewhere.

I also have another 128 (it was on sale when I got it), used for working documents.

Movies and music live elsewhere.


Go with a 256GB, and use that for OS and applications. Don't partition.
 
Solution

RavenPanther

Honorable
Sep 2, 2013
33
0
10,530
You always have great answers, USAF :]

On your Kingston 128, how much space do you ~actually~ have on it? (I'm using Windows' Disk Management screen to view how much I have, mostly because my current HDDs are partitioned.)

Mostly because I'm always, ever-curious, why exactly wouldn't you want to partition an SSD? I know one of the main reasons for doing such on a HDD was because of fragmentation, which isn't an issue on an SDD since everything is instantly-accessible.
 

USAFRet

Titan
Moderator


XShikAp.png

As said...Windows and ALL applications other than games.

As far as partitioning, I haven't seen the need for it. Now...if I had a 1TB SSD, I might. OS and apps in one, other stuff in another.