Separate partitions for OS and programs (Vista 64)?

deton8

Limp Gawd
2FA
Joined
Sep 27, 2007
Messages
485
I've got a 500gb WD drive I was thinking of splitting into partitions for my new build: (1) OS, (2) Programs/Games, (3) a spare in case I decided to dual boot, and (4) one for all those uh, Linux distros I downloaded :D

Should I bother separating the OS and programs? Or does Vista still require you to reinstall all your programs if you end up reinstalling the OS anyway?
 
there are some programs you can get away with running without reinstalling. liiiike winamp. In general I keep mine separate from the OS anyways. it allows me to keep settings and not need to actually reinstall everything. for some programs if you should have to reinstall if you have certain settings already in that folder they maybe preserved. I also generally keep my games separate from actual programs too. a lot of my old games require no reinstall. however some like red alert2 do require a reinstall.
 
Any suggestions on how much space I should leave for Vista? I was thinking 30gigs should do it, but that's just a guess on my part.
 
it suggests 33Gb if I recall correctly. which I've even come close to filling up. so use your best judgment. I've also heard of others having much slimmer installs. I couldn't tell you what they did to get a slimmer install though. things to trim down would be to keep the hibernation and pagefiles on a separate partition
 
Even if I could slim it down that far, I'd still want to leave space for system restore/windows updates/whatever other crap, right? So I probably couldn't get away with less than 15-20Gb in any case?
 
Use vLite first and clean out the crap. http://www.vlite.net/ With just the worst fluff removed you'll get down to ~5GB installed.

Hmm, been hearing about how people fuck up their Vista installs as a result of vLite. So I don't recommending using vLite, except to slipstream drivers and SP1.
 
Vista x64? If I had a 500GB drive I'd have at least 60GB set aside for the OS/system partition, then the rest as one big "storage" partition.

30GB isn't enough as with updates, software installation, the fact that Vista duplicates every system file every time one is changed and safely stashes it for backing up/reverting to prior versions, etc will make that 30GB disappear in a few weeks if not months. 60GB is a good starting point, 75GB is even better, and if you have big software suites like Office 2007 or heaven forbid the CS3 stuff from Adobe or other big apps, then perhaps the 100GB is the way to go.

I made another post recently on the coolest way to find the best amount of space:

Run HDTach on that drive, or HDTune. Look at the graph and note the speeds as the drive starts off fast and then tapers off to its slowest point at the end. Look closely at the beginning of the graph line and follow it to the right till it gets about 20% into the drive's capacity. Knowing how most drives work these days will show a nearly solid level of performance with some occasional spikes that dip low - if you re-run the test it'll be different - but the main point is there's a solid level roughly 15-20% into the drive and then the line really takes the nosedive.

Almost every drive has this type of performance curve, so my suggestion is:

Run either HDTach or HDTune, watch the line. Find the speed the drive started at, try to eyeball it, and if the line goes above that mark, stick with it until the drive goes below that mark - usually about 15-20% in - and then use that amount of space as your system partition. That ensures you are most definitely using the fastest part of that drive for the part that matters the most: the system partition itself.

Looks sorta like this:

hdtachflatlinebt6.png


The green line shows (from the left) where the test began, roughly about 62MB/s - the starting speed of the drive - and then goes up a bit, then down a bit (I've got a download in progress so that little dip was a regular write to the drive during the benchmark, was a tiny file), then it goes back up to a peak of about 67MB/s or so, then it sharply dropped because the download finished and Firefox closed out the download and NOD32 checked the file during the benchmark.

Then it shot back up and stayed a bit level to the ~60GB point, and then from that point on it's basically that downward slope I mentioned. But, as the green line indicates, the performance is consistently fast(er) from the start of the testing (aside from the dips/writes) to the ~60GB point. My system partition currently on this old Maxtor 250GB 16MB SATA I drive is actually at 35GB, so I'm well under that ~60GB point where the drive is no longer consistently averaging its fastest possible speeds.

While the 60GB point on a 250GB drive is roughly about 28% into it, I chose to drop that back a bit so I kept in under the ~20% figure I mentioned above. At least I'm absolutely sure that my OS - XP Pro x64 - always resides on the fastest part of the drive itself. The rest of the drive past the 35GB point to the end is my Storage partition, where the big stuff goes, downloads, etc. All my applications aside from Portable Firefox (on a USB stick) reside on C: with plenty of space to spare and all the speed my drive can manage.

Hope this helps, somewhat...

ps regarding vLite...

vLite can strip a shitload of gunk from Vista and make it a damned lean OS, but you have to be careful, you have to do research, and you have to read the forums to see what other people have done, what their results were, and what 'got broken' in the process.

I've got a Vista Business x64 DVD I created, it's barely got 1.1GB of files on it, it installs completely clean in about 11 minutes, and it consumes under 225MB of RAM when it first boots, then SuperFetch kicks in and takes care of the rest as required. Not a bad project I did on that one, but it did take multiple attempts, using VirtualBox, to get it the way I wanted it, as well as a DVD+RW so I didn't waste media when I actually applied it to my primary machine, a Q6600 with 8GB of DDR2 800. Works great, is fast as hell - still not as fast as Server 2008, though. :)
 
I'm currently using a 60GB partition for my OS/apps partition on my laptop and it's generally pretty full. For a primary system, I recommend a minimum of 80GB for that, and if you plan on splitting the two up, use ~25-30GB for the OS and ~50GB for apps.
 
I'm currently using a 60GB partition for my OS/apps partition on my laptop and it's generally pretty full. For a primary system, I recommend a minimum of 80GB for that, and if you plan on splitting the two up, use ~25-30GB for the OS and ~50GB for apps.

Splitting the apps onto a separate partition inside the first ~80GB of space on the drive (as you just described) means a shitload of unnecessary head movement and that hampers performance drastically. No matter how much optimization takes place, the heads will still have to move deeper into the platters to execute your applications, and not at the beginning of it where they should be. Here's why:

If you're going to do it right, do ~80GB and put the OS and the apps there, that will ensure the apps are right there at the beginning of the drive completely without needing to do this:

a) Load an OS file like a .dll of some kind inside the 30GB system partition.
b) User requests an application load from the secondary partition so the heads have to jump to a point somewhere around 31GB or deeper
c) The application needs another OS .dll during the loading as its tied some OS .dll files - head has to jump back to around the 2GB point in the drive's capacity - a big jump backwards
d) More of the application needs to load so back to the secondary partition now 32GB in
e) Something from the OS needs to load to manage files or memory or whatever so back to the < 5GB point at the beginning of the drive

etc... back and forth back and forth, it gets ridiculous.

Put it all inside the 80GB and it's all on the same partition, the OS consumes a chunk of space as required, and over time - we're talking about Vista here but this applies to XP as well - when the OS defrags itself it'll bring the most commonly and frequently accessed files on the entire ~80GB partition to the beginning of the platters or close to it. See how this works?

People will say it doesn't matter under Vista because of SuperFetch, but ah... that's where they're wrong.

As the OS boots, the SuperFetch cache is preloaded during the OS loading, soo... when the computer boots, it'll have to hit the dead beginning of the drive to get the OS loaded and keep jumping to the secondary partition - at least 30GB into the partition - and back, and forth, and back, and forth as the OS is fighting to load with the SuperFetch data which resides on the secondary partition because you didn't put it all in the same damned place to start with.

When everything works right, Vista will, during a defrag pass, move the most frequently accessed files to the beginning of the drive over time, including the most frequently loaded .dll files, the application .exes, all the stuff that gets loaded the most frequently. Hence, that's why some people tell you Vista boots FASTER over time than it did when they first started using it, even with SuperFetch.

It really is a damned smart OS if people just let it do its job and self-tune without bothering it. It really does get faster over time but yes, there will come a point where the returns on the self-tuning are flat, but they should not slip and become under-performing unless the user fucks with it in some way.

It'll get to a point where it's as fast as it can be and maintain that level given the specific "static" platform the OS works on. Alter something, change hard drives, CPUs, mobos, etc, and you alter the equation so it starts over again, self-tuning back to the optimal state.

People should know this shit by now, Vista has been out well over 1.5 years now... come on.
 
Splitting the apps onto a separate partition inside the first ~80GB of space on the drive (as you just described) means a shitload of unnecessary head movement and that hampers performance drastically. No matter how much optimization takes place, the heads will still have to move deeper into the platters to execute your applications, and not at the beginning of it where they should be. Here's why:

*snip*

I never suggested that the OS and application partitions be split up, merely that if the OP chose to do so for whatever reason, he should have at least a 25-30GB partition dedicated to the OS. I personally would not do this, and like I said, I already use a single partition for the OS and programs, and another for data.
 
So if you wouldn't personally do it, why would you recommend such an action? Just curious considering how much of a performance hit it might cause...
 
So if you wouldn't personally do it, why would you recommend such an action? Just curious considering how much of a performance hit it might cause...

Because I didn't recommend it, which you can easily see by reading my post. I merely offered the OP my suggestion regarding how he should split up the partitions if he did decide to go that route. However, I never said anything about recommending it.
 
Back
Top