I have 35GB partitions in my 250GB FHDs . . . and partitioning ISN'T a thing you do when "you require more" space . . . you do it ONCE, when you first put a new FHD into service. And BTW, it's MUCH faster looking for a file in a 35 GB partition than in a 250GB FHD!
You seem to have miss understood me. A partition is like segmenting a drive. If you've got a 100gb drive and you put it into two segments you should end up with two 50gb segments which present them selves in the operating system as separate 50gb drives. There are many reasons for partitioning, but decreasing seek time is not one of them. See, performance is decreased due to the fact that data requested simultaneously from the separate partitions will in fact half in read time due to the HDD head needing to perform twice the amount of operations. Even if you're just sitting there doing mixing from a single partition and not touching the other one, the operating system is still asking for information from the other partition.
If you want to reduce your seek times, just use it as a single drive. Just use a folder filing system. It also means that if for some reason your project went over 35gb, that you wouldn't have to go make a new partition (afaik partitions are generally fixed in their size.

).
I don't wanta' start a "pi$$ing contest", but I've "been around computers" quite a bit longer than you've been ALIVE!
That's fair enough.
But random-access audio recording, editing and mixing IS "heavily dependent on seek" times . . .
On the note of recording, no. It's not segmented. If you've ever wondered why you have to defrag your HDDs every now and then it's because the drive doesn't write all your files in a nice pretty line on the disk. They get scattered around. With audio recording you could be doing gigs of data recorded directly to a disk, and the disk doesn't care where it's recorded, it just slaps it down. This reduces the importance of seek on write operations.
On editing and mixing, yes. It's more seek dependent than recording, but it's also not as VITAL to have a fast seek time that you shell out a bomb on a 10k Raptor drive specifically for it. The slight difference between Raptors and 7.2k drives. When you open a cubase project or the like, most the "loading" time isn't even seek related. It's data transfer, memory and CPU related. Sure, when you're snipping bits here and there it'd be nice to have 10k raptors set up in a raid array to reduce your seek massively, but it's not that damn important and certainly not worth the price tag. For a data base that's receiving 1000 requests for information, a 10k raptor drive is a god send. For audio editing, you're better off getting a decent CPU and a mass chunk of memory because they're far more important than disk seek could ever be.
Also, when you work with large volumes your seek time is greatly reduced. So if you're running a 400gb disk cut into 20 partitions of 20gb, your seek time has pretty much gone out the window anyway...
FWIW, ALL of the external hard drives at the studio that I work at have BOTH USB AND Firewire interfaces. And most of them have BOTH 400 AND 800 firewire . . .
That's fair enough. The fun one will be USB3.0. That baby cranks out 4.7Gigabits/s. That's 602MB/s! Most of which will never be used by a hard drive...Not until solid state comes into the equation. Oh those look fun.
Edit: It's also worth mentioning that Audio / Video editing is HEAVILY CPU/Memory reliant. It'd be better to have an Intel Q6600 and 3GB of memory (max 32bit OS's allow) than a rack of 10k raptors.
Edit 2: In fact, your best bet for good bang for buck is to take a load of cheap and reliable drives and put them in a raid array.