Post Reply 
Partitioning Guidelines
Author Message
ZiNgA BuRgA
Smart Alternative

Posts: 17,022.2988
Threads: 1,174
Joined: 19th Jan 2007
Reputation: -1.71391
E-Pigs: 446.1274
Offline
Post: #1
Partitioning Guidelines
Have been setting up a new computer, so I thought I'd take the opportunity to write this up.

I've seen many people still just simply set up their system with a single partition and dump everything onto it.  This guide will try to show you some reasons why you might want to partition.


Actually, this is primarily directed at those with large HDDs, who would rather performance at the cost of some space usage.

Probably isn't worth you going to rip up your current setup and repartition everything, but might be something you want to do when you set up a new system.



Why Partition?
Current hard-drives' biggest problem, in terms of performance, is seek time (time it takes for the HDD to spin to a specific location and retrieve the data you're after) - until SSDs become more commonplace, this is something wee'll have to live with.  And fragmentation simply makes seek times worse, thus it makes sense to try to avoid fragmentation as much as possible.

Sure you can defrag once a while, but I doubt most people do it terribly often - instead, wee try to avoid it as much as possible.

Partitioning can help reduce fragmentation, or fragmentation on certain parts of your setup.

About Fragmentation
Simply, fragmentation generally occurs once the HDD has filled up all the physical space, and then, usually when you're running low on free disk space on a drive, the OS will try to fill up all the gaps when writing new files (which will be fragmented).  (sorry for bad explanation)  Note that the amount of physically unused space on the HDD will decrease over time, and eventually, files will become more fragmented.

So if you simply just have a single drive setup, with your files and apps, fragmentation can build up rather quickly on the drive.

Idea behind partitioning
...is to separate stuff that isn't commonly written to, and is read a lot (ie system files, and applications) with stuff that you often write to (ie when you're dumping a DVD to the hard-drive).  As you can probably see, the less writes, the less fragmentation.

The other thing to keep in mind is free space.  Don't partition so that you just have enough room to fit what you need to - if you've got a large HDD (somewhat the case these days), leave plenty of breathing room for any future writes.

Here's an example of a general partitioning structure I adopt:
- Windows XP  [20GB]
- Backup Windows  [12GB]
- Applications/Games  [100GB]
- Files  [200+GB]
- Temporary Storage  [150GB]
- Spare space  [~50GB]

The idea is that the OS is installed to the first partition.  20GB is more than enough storage for a stripped version of XP, the paging file, hibernation file, and any future libraries installed.  This partition rarely ever gets written to, thus will usually be pretty much unfragmented.
The temporary storage is where I dump DVDs, or copy stuff that will only be on the HDD for a short while (though I'm somewhat lazy, and leave things there, which is why I make the Temp store a bit big-ish).


Other advantages of partitioning
  • Can save you from hassles of having to repartition your HDD later on when you want to try a new OS (plan your structure before committing it)
  • If you later get a new HDD, it's easier to move the partition across - ie, if you get an SSD (which is excellent at reads, though writes don't do them so well), you can move your OS drive directly to it.
  • Can make some things more convenient (ie storing your apps on "G:\" - it's quicker to type that than "C:\Program Files")


Formatting
Yet another advantage of partitioning is the ability to format each of them optimally for the partition's purpose.
Generally, on Windows, you'd probably use NTFS (though for a file storage partition, if you use other OSes as well, you may wish to make it a file format supported by both OSes).
The other thing to consider is block/cluster/sector size (they're just different names for the same thing).  Larger block sizes generally mean faster access at the expense of disk space (larger block sizes also allow larger partitions).
So for your system drive, and a temp file storage drive, try to use the largest block size possible for maximum speed (as long as you're not going to put a tonne of small files on them).  You'll probably want to use a smaller block size for file storage.


Considerations for a Windows drive
A problem when setting up Windows is that you can't choose the block size during setup.  This means that you have to set the partition up before installing Windows (make sure you don't format the drive during setup though).
Another problem is the fact that a lot of things can still get written to your system drive (mainly Application Data, badly written apps hard-coded to install into your Program Files directory, Temp files etc).
A simple solution to solve these is to use NTFS junctions - I'll probably write a tutorial on how to do this later.  Also, for the temp folder, you could consider setting it to a RAMDisk (will probably also write a tutorial on that later too).
14/12/2008 05:40 AM
Visit this user's website Find all posts by this user Quote this message in a reply
Nacos
Soon to be Moderator?

Posts: 2,004.2538
Threads: 181
Joined: 21st May 2007
Reputation: -0.41086
E-Pigs: 12.1482
Offline
Post: #2
RE: Partitioning Guidelines
Good stuff, but I really liked partitioning too much hassle imo.. I keep a neat file structure so im good :)

[Image: 17312564gf1.png]
14/12/2008 05:42 AM
Visit this user's website Find all posts by this user Quote this message in a reply
Vegetano1
$urf

Posts: 9,083.2507
Threads: 397
Joined: 2nd Mar 2007
Reputation: 6.06988
E-Pigs: 2756.6280
Offline
Post: #3
RE: Partitioning Guidelines
- Temporary Storage  [150GB]

i prob got like 2 terrabyte of temp storage,. ;p

when installing windows,. i was wandering,.  the setup prob uses the best blocksize for a win install,.!>?

also i dunno if this is topic related but i got a 720 gig external hard-drive and windows wants to check for errors,. the disk can't be checked when windows is running because its in use,.!!>? so win starts a check on start-up,. i have tried this but after 4 hours it was still at 33%,. > :( is there anyway to get this disk checked quicker or within windows,. and disabling somehow all appz using the drive,.>!?


Make loads of $$!! it wurks!!
[Image: csbanner_anim_03.gif]
Signed Homebrew by bsanehi & OMightyBuggy
http://endlessparadigm.com/forum/showthr...?tid=25707
Spoiler for My miniBlog:
14/12/2008 05:52 AM
Visit this user's website Find all posts by this user Quote this message in a reply
Assassinator
...

Posts: 6,646.6190
Threads: 176
Joined: 24th Apr 2007
Reputation: 8.53695
E-Pigs: 140.8363
Offline
Post: #4
RE: Partitioning Guidelines
Heh, my HDD is a complete mess. Years of poo poo built up (+ a few old computer's files all dumped in there).

Fragmented so bad that the last time I did a defrag analysis, there was a file fragmented ~88,000 times, and half the list is 10,000+.
14/12/2008 03:27 PM
Find all posts by this user Quote this message in a reply
PSPkiller
*The Sweaty Indian/Welsh Guy*

Posts: 2,393.2167
Threads: 251
Joined: 24th Jun 2007
Reputation: 0.56947
E-Pigs: 53.7911
Offline
Post: #5
RE: Partitioning Guidelines
I just have seperate drives for everything.

I have a 320Gb Sata drive for OS and apps (seperate partition for both),
a 160Gb IDE drive for general storage (media/documents) and an 80gb Sata drive for age file and temporary storage (seperate partition for both)

[Insert Signature Here]
15/12/2008 08:56 AM
Find all posts by this user Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 2 Guest(s)

 Quick Theme: