ssd drive question

Hi Guys

Does the OS need to be on the same SSD drive as DCS world and also is it just a case of simply cloning the DCS files from my excising drive

thanks

No, OS on one SSD, Games/Apps on another is a good way to go.

No, OS one one SSD, Games/Apps on another is a good way to go.

Would a partition suffice?

I will be getting the 970 Pro, M.2, 1 TB, plenty for OS and a few games.

Motherboard will probably be the Asrock Phantom 9 which has 3 M.2 slots.

I wouldn't bother fluffing about partitioning the drive and 1TB is more than enough for OS and DCS. Putting DCS on a second drive is more a personal choice maybe if you had smaller SSDs.

Besides as I understand it partitioning your drive.will add more overhead to the file system for no real benefit.

YMMV :smartass:

I wouldn't bother fluffing about partitioning the drive and 1TB is more than enough for OS and DCS. Putting DCS on a second drive is more a personal choice maybe if you had smaller SSDs.

 

Besides as I understand it partitioning your drive.will add more overhead to the file system for no real benefit.

 

YMMV :smartass:

+1 on the no partition. It made sense in the old days with limited MBRs etc. But nowadays, there' no real need for it. I'm excluding the partitions that are useful like recovery partition etc. But those are done automatically when you install Windows or other backup software.

I wouldn't bother fluffing about partitioning the drive and 1TB is more than enough for OS and DCS. Putting DCS on a second drive is more a personal choice maybe if you had smaller SSDs.

 

Besides as I understand it partitioning your drive.will add more overhead to the file system for no real benefit.

 

YMMV :smartass:

:thumbup:

@ Demon_ Merci. :) :thumbup:

Don't thank me, thank you. :smilewink:

I've never experienced any adverse performance effects from partitioning. 1 good reason to partition is so you can isolate the OS and programs/data from each other. Sooner or later there will be a crash you can't recover from. Regular backup images of each partition allow you to restore The OS to a recent, known good state without having to reinstall all of your programs and vice versa. On my own system, I let small, trivial, insignificant programs go wherever Win wants to put them, but large, complex programs that are not easily replaced live on a separate partition. In my case, that partition is also on a separate hard drive. I make regular, independent backup images of each partition on each drive to yet another drive whose only purpose is to host backup images. In the event of a failure (everything fails eventually) I can have everything up and running, just like it was, in around a couple of hours max. At least as it was at the time of the last backup, which is why that needs to be done regularly. At worst I'll need to reapply a few updates to the OS or a few programs, but I won't have to rebuild my entire system, which, in my case, would require at least 2 solid days of doing nothing but that. I highly recommend isolation and compartmentalization of OS, programs and data and regular backup images of each partition and drive to a separate dedicated drive.

That used to be the best practice and made a lot of sense. Today, though, the benefits are marginal, at best. Just the partition failing is so rare that I've never heard of it. OS corruption does happen, enough so that it's not a surprise when it happens. But Windows recovery allows you to reinstall w/o nuking the disk these days.

There is *not* downside to what you're suggesting. Modern day PC doesn't slow down nor get faster with multiple partitions. And unused space of few hundred GB is not a big deal. You do need plenty of space for the OS partition because the next upgrade may require 20-40 (who knows?) GB to make room for backout, the actual upgrade etc. But again, the decision is 50/50. I mean every modern Windows has three partitions already (EFI, OS, and Recovery). Adding one more won't make a difference either way.

So net/net, pick whatever method you feel more comfortable with.