Tom's Hardware > Forum > Storage > Hard Disks > Raid vs raptor
Word :    Username :           
 

Last message on previous page:
I just built a PC a month ago with 2 WD Raptor 10,000 RPM 150 GB drives and placed them in a RAID 0 configuration using an onboard Nvidia Controller on an ASUS A8N32 SLI motherboard.

I also have a WD 400 KD hard drive. I use the 400 GB drive for storage & backups, and the RAID 0 array (300 GB total) for Windows & games.

For the nay-sayers (read: RAID non-conformists), after using RAID for over a month now, I can wholeheartedly agree that RAID offers advantages in speed and latency over a single drive. If you play games, RAID is highly recommended! If you play Battlefield 2, you know what I mean when I say that load times are not a deal breaker, but are damn annoying when you want to get into a game. Don't mind waiting 60+ seconds for the game to load? You're more patient than I am.

Frankly, I can't think of a reason NOT to have RAID if you are a gamer. As long as you back up critical data, you are 100% safe if hardware crashes. You see, other components can fail too...which is another reason to back up your data. I had lightning strike my computer, so I learned that lesson...but I digress.

If you want to see actual numbers, read Maximum PC. Every month it seems, they do benchmarks on all kinds of hard drives both with and without RAID, using HD Tach and other benchmarks.

I will echo the sentiment that cost is NOT the factor for hardcore gamers like myself. We have to have the best, cost be damned. If there was room in my PC to do a SCSI RAID 0, trust me, I'd do it!

Reply to silverfrog
Sponsored Links
Register or log in to remove.
- 0 +

Quote :

Yet you'll depend on less reliable raptors than slower more reliable 7200 rpm HD and much faster SSD.


Less reliable? How exactly are they less reliable then a 7200rpm drive? I have had countless 7200rpm drives, with a fair share of problems, to be expected though over time with a lot of hard drives. Now my oldest raptor is about 3 years old and I have not had a single problem with it, I also have a 74gb and 150gb raptor that work flawlessly. The raptors also have a 5 year warranty on them. Personally I don't keep stuff that long generally so it works for me. I suppose if you plan on keeping a hard drive for 10 years them maybe it's different for you.



The fact is the slower rpm drive has in theory, built with the same tech, a longer life due to less heat and wear on the spindal. True the raptor has a longer warranty but more due to higher price tag. I have a 5400rpm western digital working for some 10 years now. When combined with software SSD the life of any drive will greatly increase as it acts as a much larger cache greatly decreasing number of hits to the primary drive.
Software SSD is near the fastest SSD doing about 80X that of any hard drive and the software only costs is $49.
http://www.cenatek.com/store/morei [...] N=11155387
Iram is a good SSD but only about 6X that of any hard drive but it can hold 2x, with 1 iram or 4x with 2 iram cards, of the current motherboard based software SSD. Iram's best parts is battery backup and can boot your OS for around $100 plus the RAM. Will make a great use of your old DDR once you move to DDR2 memory.
http://techreport.com/reviews/2006 [...] dex.x?pg=1
I use the 7200rpm drive and software SSD due to an equal price point to 2x 74Gb raptor raid. While a raptor primary drive would be some faster with a software SSD I would say the SSD is far more important in the build for a gamming system.

Reply to elbert

Sorry for the double post. THG has been slow today and I guess I hit submit twice by accident!

Reply to silverfrog
- 0 +

silverfrog why did you submit it twice? Raids nice but for gamming software SSD should come before the second drive.[/quote]

Reply to elbert
- 0 +

Quote :


The fact is the slower rpm drive has in theory, built with the same tech, a longer life due to less heat and wear on the spindal. True the raptor has a longer warranty but more due to higher price tag. I have a 5400rpm western digital working for some 10 years now. When combined with software SSD the life of any drive will greatly increase as it acts as a much larger cache greatly decreasing number of hits to the primary drive.


That would only be true if the software SSD either 1) slowed down the drive or 2) spun the drive only when needed.
Otherwise, the drive will still spin when the system is on and still have "heat and wear on the spindal". Not to mention the motor, other components, etc.
In addition, adding tons of cache is not always beneficial because the system must spend time searching the cache for the information. Obviously there's several ways to minimize the impact of the search, but the fact remains that searching a 8MB cache is faster than searching a 512MB cache.

A thought might be to hold enough data in the HDD's software SSD to offset the need to wait for the head to move to the correct position/sector - the average seek time.

Reply to nobly
- 0 +

Quote :

n addition, adding tons of cache is not always beneficial because the system must spend time searching the cache for the information. Obviously there's several ways to minimize the impact of the search, but the fact remains that searching a 8MB cache is faster than searching a 512MB cache.


True but in this case were talking about a 2 to 3Gb software SSD than can hold mostly all of any game. The software drivers for the SSD wouldn't even take the time to check the HD but stop at the RAM where the software SSD has the files.

Quote :

A thought might be to hold enough data in the HDD's software SSD to offset the need to wait for the head to move to the correct position/sector - the average seek time.


In most games thats the case but a few will come with more that 3Gb's which the fact of RAM being 80X times faster than a HD will only slow it to say 75X the fastest HD.

Reply to elbert
- 0 +

I think I misunderstood your post.
Are you talking about using SSD as a replacement for HDD cache (I understood it that way) OR are you saying there will be, in essence, 2 logical HDD's (1 SSD, 1 disk drive) on 1 physical drive?

If it is indeed the 2nd version, the HDD will have to draw power from the PSU and would still be fallible due to power loss. Its just the same as it is now... No difference except that its just 1 physical unit instead of 2 like it is today.

Reply to nobly
- 0 +

Quote :

I think I misunderstood your post.
Are you talking about using SSD as a replacement for HDD cache (I understood it that way) OR are you saying there will be, in essence, 2 logical HDD's (1 SSD, 1 disk drive) on 1 physical drive?



Yes, I would could have guessed you misunderstood. The software SSD, works off system RAM and, cannot replace the HDD and requires a primare HDD.

Quote :

If it is indeed the 2nd version, the HDD will have to draw power from the PSU and would still be fallible due to power loss. Its just the same as it is now... No difference except that its just 1 physical unit instead of 2 like it is today.


RAM, the type I use anyway, has a lifetime warranty and should last 12 times longer than hard drives. True, it just have 1 HDD but after boot for any give game the hard drives job is done and the SDD take over saving the hard drive from all the massive loads of the different boards. The big difference is the SDD is 80X times faster than a raptor which cuts the boards load time, from 20+ second with HDD's, to only about 1 second.

Reply to elbert
- 0 +

Oh, so you're basically just talking about like a RAM disk. Sorry, my bad. I think everyone here is trying to figure out what you are talking about with the 'software SSD'. Its hard contextually to distinguish because everyone's throwing around iRAM and SSD terms.

So you're saying it would preload the game data on the RAM disk to aid in faster access and faster load times.

In essense, you can't compare a RAM disk to a HDD in terms of reliability. They're different and used for completely different things. Software SSD, by your description, is just a preload-ed iRAM on an application startup (RAM disk).
Which may help for data access, but the fact remains that you must preload the data, which helps in game, but it won't that much if it only preloads the levels, and if it preloads the entire game, it seems to be a waste unless you're going to play every single map on there. And what you don't preload, you must go to disk to retrieve.

I would say you shouldn't use "SSD" to describe software SSD. SSD by definition has a battery backup of some sort because it stores data on volatile memory.
http://en.wikipedia.org/wiki/Solid_state_disk

Quote :


Since these SSDs use volatile memory, they typically incorporate internal battery and backup disk systems to ensure data persistence.



http://en.wikipedia.org/wiki/RAM_disk more fits what you're describing, at least from my viewpoint.

Reply to nobly
- 0 +

Quote :

In essense, you can't compare a RAM disk to a HDD in terms of reliability. They're different and used for completely different things. Software SSD, by your description, is just a preload-ed iRAM on an application startup (RAM disk).


Sure you can when it extends the life of your boot drive. IRAM is different its a memory card with battery backup which can boot and connects via SATA buts much slower than a software SSD setup on system RAM.

Quote :

Which may help for data access, but the fact remains that you must preload the data, which helps in game, but it won't that much if it only preloads the levels, and if it preloads the entire game, it seems to be a waste unless you're going to play every single map on there. And what you don't preload, you must go to disk to retrieve.


Preloading the levels is infact what you should preload as most of the game engine code an such is already going to be in normal system RAM. True, what you dont preload must be retrieve from the HDD but the part preloaded moves at 80X will make the entire game faster than any drive raid.

Quote :

I would say you shouldn't use "SSD" to describe software SSD. SSD by definition has a battery backup of some sort because it stores data on volatile memory.


SSD is Solid State Disk and is the correctly define the RAM drive. SSD's or all volatile and the only real requirement is its made of RAM. The ones with batterys are simply bootable SSD's and if they loss power they too loss there data just like system RAM.

Reply to elbert

Quote :


The fact is the slower rpm drive has in theory, built with the same tech, a longer life due to less heat and wear on the spindal. True the raptor has a longer warranty but more due to higher price tag. I have a 5400rpm western digital working for some 10 years now. When combined with software SSD the life of any drive will greatly increase as it acts as a much larger cache greatly decreasing number of hits to the primary drive.


That would only be true if the software SSD either 1) slowed down the drive or 2) spun the drive only when needed.
Otherwise, the drive will still spin when the system is on and still have "heat and wear on the spindal". Not to mention the motor, other components, etc.
In addition, adding tons of cache is not always beneficial because the system must spend time searching the cache for the information. Obviously there's several ways to minimize the impact of the search, but the fact remains that searching a 8MB cache is faster than searching a 512MB cache.

A thought might be to hold enough data in the HDD's software SSD to offset the need to wait for the head to move to the correct position/sector - the average seek time.

Yes, but which is faster....searching 512 MB of cache or 512 MB of hard drive platter? I think you'll discover where I'm going with this. Having more cache on the hard drive is better 100% of the time. Saying that having 8 MB of cache is better than 16 is rediculous. That's like saying having 1 GB of memory instead of 2 GB is better because it takes less time to search 1 GB of system memory than it does for 2 GB. If that were true, no one would upgrade!

Reply to silverfrog

Quote :

SSD is Solid State Disk and is the correctly define the RAM drive. SSD's or all volatile and the only real requirement is its made of RAM. The ones with batterys are simply bootable SSD's and if they loss power they too loss there data just like system RAM.



But those drives have batteries and external PSUs, whereas a software solution can't provide that kind of extra protection.

Again we need to think about pricing here, $2/gb for a Raptor is a LOT of money (when you can get in the UK a 250gb drive @ £0.24/gb). Solid State memory is even more - £50/gb is not really a reasonable price to pay.

As for saying 8mb of hard disk cache is faster than 16mb?

Hey, I've got an old 40mb drive with about 64k disk cache, it's rocketship fast.

Reply to mesarectifier
- 0 +

Quote :

So your saying my less than 1 second load time for counter strike source map is not viable.


what if the battery goes out? what if you dont have a backup of your data? what if an average user doesent have a backup? the last thing an average user will think is backup

Reply to jap0nes
- 0 +

Quote :

But those drives have batteries and external PSUs, whereas a software solution can't provide that kind of extra protection.


So true but its also near the fastest and is the cheapest.

Quote :

gain we need to think about pricing here, $2/gb for a Raptor is a LOT of money (when you can get in the UK a 250gb drive @ £0.24/gb). Solid State memory is even more - £50/gb is not really a reasonable price to pay.


Yet you'll be upgrading your memory on the 939 mobo. Lets face it the DDR400 1Gb memory are about as low a price as they ever will be.

Quote :

As for saying 8mb of hard disk cache is faster than 16mb?


Wasn't I that said it but someone did say 8mb took less time to search than say 512mb.

Quote :

Wrote by nobly:
That would only be true if the software SSD either 1) slowed down the drive or 2) spun the drive only when needed.
Otherwise, the drive will still spin when the system is on and still have "heat and wear on the spindal". Not to mention the motor, other components, etc.
In addition, adding tons of cache is not always beneficial because the system must spend time searching the cache for the information. Obviously there's several ways to minimize the impact of the search, but the fact remains that searching a 8MB cache is faster than searching a 512MB cache.


Its true due to its less cache to search but searching 512mb of cache is faster than searching an HD.

Reply to elbert

Quote :

Yet you'll be upgrading your memory on the 939 mobo. Lets face it the DDR400 1Gb memory are about as low a price as they ever will be.



I'm not sure I understand the first bit of that post.

Anyway, DDR400 1gb has reached as low a price as it can because it's already been superceded by DDR2 for all manufacturers.

And I don't see how 'cheapest DDR ever' makes up for the fact that £50/gb is still a lot of money. Especially for something that isn't really useable in the real world (yet)

Reply to mesarectifier
- 0 +

Quote :

jap0nes
PostPosted: Wed May 17, 2006 11:06 pm Post subject: Re: Raid vs raptor
Quote:
So your saying my less than 1 second load time for counter strike source map is not viable.

what if the battery goes out? what if you dont have a backup of your data? what if an average user doesent have a backup? the last thing an average user will think is backup


When the SSD doesn't boot then it will go down the line which should be your HD. You then see nothing on your SSD and say crap i'll have to buy a new batter. The SSD should only hold a copy of whats on your HD. The software for the SSD should by default only copy the data. For bootable SSD's they update by defualt on a schedule. If a bootable SSD software should note any changes in it and the HD at boot, say from a power loss, and will correct it at that time. For the software SSD I suggest you should never place a database for say counter strike's WC3 mode, save games, or rankings of any kind to it.

SSD's may not at this point be for average users but neither are raids.

Reply to elbert

This subject has been brought up time and time again in this forum. Raid will offer you no real tangable data access improvement, particularly with respect to gaming, and will increase your risk of data loss.

Better to go with a 10k rpm raptor, you will get equivalent or better performance than the raid, a much simpler setup and you will save $$ to boot.

I dont have any links readily available (and I havent read this entire thread, just the first half dozen responses) but I am sure with a little reasearch you will come to the same conclusion that raid is NOT the way to go unless you want data redundancy, in which case Raid 0 would not be your choice anyway.

Reply to Preecher
- 0 +

Quote :

Quote:
Yet you'll be upgrading your memory on the 939 mobo. Lets face it the DDR400 1Gb memory are about as low a price as they ever will be.




Quote :

I'm not sure I understand the first bit of that post.

Anyway, DDR400 1gb has reached as low a price as it can because it's already been superceded by DDR2 for all manufacturers.

And I don't see how 'cheapest DDR ever' makes up for the fact that £50/gb is still a lot of money. Especially for something that isn't really useable in the real world (yet)


The software SSD I'm suggesting uses The systems RAM. After say programs use to much of the systems RAM to make a software SSD then you could just use the extra, RAM you install for the SSD, for just system RAM. Todays Games want use all of a fully loaded 939 mobos maxed out RAM. Use the rest over what the games use as a SSD and you'll only be out the cost of the software, which is $49, to set it up.

Reply to elbert

But with programs as they are today, you'd likely only be left with 3-400mb? Which about enough to install Q3A onto, but not Oblivion.

Which would leave you buying extra RAM.

Reply to mesarectifier
- 0 +

Quote :

This subject has been brought up time and time again in this forum. Raid will offer you no real tangable data access improvement, particularly with respect to gaming, and will increase your risk of data loss.

Better to go with a 10k rpm raptor, you will get equivalent or better performance than the raid, a much simpler setup and you will save $$ to boot.

I dont have any links readily available (and I havent read this entire thread, just the first half dozen responses) but I am sure with a little reasearch you will come to the same conclusion that raid is NOT the way to go unless you want data redundancy, in which case Raid 0 would not be your choice anyway.


I agree 1 raptor is the best and a software SSD which would show a tangable data access improvement.

Reply to elbert
- 0 +

Quote :

But with programs as they are today, you'd likely only be left with 3-400mb? Which about enough to install Q3A onto, but not Oblivion.

Which would leave you buying extra RAM.


Only load the parts of the program that want be in the rest of your system memory. For say counter strike source that would be the maps you like to play and your swap drive is all I load.
True but at some point you'll have to buy that extra RAM anyway. I say buy it now and get the added performance of software SSD while you can. In the long run it'll only cost you the $49 for the software and its faster than a raptor.

Reply to elbert
- 0 +

OK, everyone, Elbert is talking about a RAM Disk. Its not a SSD like iRAM, its not really a SSD at all. Its a RAM Disk. Its kind of preselecting what you want to be in system RAM.

@ silverfrog,
No, I'm not talking about searching 512MB on a HDD platter either... Besides, you don't search on a HDD platter - you know the address where it is, so you just drive there. Its a big picture of performance. There is a point where too much cache is more costly than than less cache.

Say the CPU requests data. First the system checks system RAM for it, right? (I assume the CPU wouldn't request data if it was in the CPU's caches). Secondly, if it doesn't find it in system RAM, it asks for it from the HDD.
So first, the HDD searches its cache for the data, right? That's why the cache is there. But if it doesn't find the data, you've lost time searching the cache when you could have been retrieving data.
So:
(average time to get data) = (% of cache hits)*(time to access cache) + (% of cache misses)*(time to retrieve data from disk)

So when the cache does not contain the data, you lose (% of cache hits)*(time to access cache) amount of time. The bigger the cache, the bigger the (time to access cache) is. Once the (time to access cache) = (time to retrieve data from disk), what's the point of having cache? So there is some point where having too much cache is detrimental to performance. Do you see my point?

Its more applicable in the CPU cache/memory subsystems than the HDD, but in principle its similar. Ask why don't we have a 2GB L3 cache? Because to search that 2GB of L3 cache is probably more costly than just going to the system RAM to get the data.

Why don't you think they can have more than 16MB of cache on a HDD now? I'm sure they could throw on 128MB w/o any problems... Perhaps the law of diminishing returns? And if they're just "holding out" on everyone, why aren't 32MB+ caches popping up in mainstream HDDs?

Reply to nobly
- 0 +

Quote :

OK, everyone, Elbert is talking about a RAM Disk. Its not a SSD like iRAM, its not really a SSD at all. Its a RAM Disk. Its kind of preselecting what you want to be in system RAM.


No, a RAM Disk is using RAM as cache in which the OS, DOS in this case, only places data in. Windows created RAM Disk and no longer even supports it.

Quote :

No, I'm not talking about searching 512MB on a HDD platter either... Besides, you don't search on a HDD platter - you know the address where it is, so you just drive there. Its a big picture of performance. There is a point where too much cache is more costly than than less cache.


I know your not and I said its true that searching 16mb of cache is faster than 512mb cache but its faster to search 512mb of cache than 16mb of cache plus 496mb or hard drive space. Searching cache is timed in the nanosecond and searching HD's are timed in the millisecond thus cache is searched faster.

Quote :

Its more applicable in the CPU cache/memory subsystems than the HDD, but in principle its similar. Ask why don't we have a 2GB L3 cache? Because to search that 2GB of L3 cache is probably more costly than just going to the system RAM to get the data.


More cost but not quicker. Cache on the CPU has faster access time than RAM but its a trade of the more cache the less room for other parts of the CPU like ALU. 2Gb of cache would take up alot of the CPU.

Quote :

Why don't you think they can have more than 16MB of cache on a HDD now? I'm sure they could throw on 128MB w/o any problems... Perhaps the law of diminishing returns? And if they're just "holding out" on everyone, why aren't 32MB+ caches popping up in mainstream HDDs?


Your correct in they can have more cache than 16Mb but the band width of the SATA limits its worth. The Iram uses the SATA and its the slowest being only about 6 times faster while software SSD is 80 times faster than any HD. The more cache the greater the cost of the HD, really the only thing hard drives have over SSD's is price, thus increasing the worth of SSD's and sales as you add cache.

Reply to elbert
- 0 +

Quote :


No, a RAM Disk is using RAM as cache in which the OS, DOS in this case, only places data in. Windows created RAM Disk and no longer even supports it.


Its practically for all intents and purposes a RAM Disk. You preload it w/ whatever you want. Its using the system RAM... It might not fit the exact description of a RAM Disk, but its pretty much doing the same thing.

Quote :

Only load the parts of the program that want be in the rest of your system memory. For say counter strike source that would be the maps you like to play and your swap drive is all I load.



Quote :


No, I'm not talking about searching 512MB on a HDD platter either... Besides, you don't search on a HDD platter - you know the address where it is, so you just drive there. Its a big picture of performance. There is a point where too much cache is more costly than than less cache.


I know your not and I said its true that searching 16mb of cache is faster than 512mb cache but its faster to search 512mb of cache than 16mb of cache plus 496mb or hard drive space. Searching cache is timed in the nanosecond and searching HD's are timed in the millisecond thus cache is searched faster.

Again, you do not search HDDs... The head moves to the address given by the master table and you just read from there. I said it before, I'm saying it again. HDD's are done in ms because that is the seek time. Seek time is not search time. Your HDD does 1 seek to drive to a point on the HDD that contains the data. Thats it. It doesn't search the entire drive for your data.

Quote :


Its more applicable in the CPU cache/memory subsystems than the HDD, but in principle its similar. Ask why don't we have a 2GB L3 cache? Because to search that 2GB of L3 cache is probably more costly than just going to the system RAM to get the data.


More cost but not quicker. Cache on the CPU has faster access time than RAM but its a trade of the more cache the less room for other parts of the CPU like ALU. 2Gb of cache would take up alot of the CPU.

That was a rhetorical question... Besides, they can make the CPU as big as they want. (yeah yeah, yields, etc etc, i know.) I was using some exaggeration to make a point. I was giving an example to show my point.

Quote :


Why don't you think they can have more than 16MB of cache on a HDD now? I'm sure they could throw on 128MB w/o any problems... Perhaps the law of diminishing returns? And if they're just "holding out" on everyone, why aren't 32MB+ caches popping up in mainstream HDDs?


Your correct in they can have more cache than 16Mb but the band width of the SATA limits its worth. The Iram uses the SATA and its the slowest being only about 6 times faster while software SSD is 80 times faster than any HD. The more cache the greater the cost of the HD, really the only thing hard drives have over SSD's is price, thus increasing the worth of SSD's and sales as you add cache.
Why does SATA bandwidth limit its worth? Since SATA has versions from 150MB/s to 300MB/s, the burst from the cache could be greater than it is now. Please explain how you got that?

Cost? We're talking about going from 16MB to 32MB of cache... Sure, I can see the cost going up if it was like 512MB or 1GB, but an extra 16MB?? Maybe an extra 20 bucks?
Here's 2 seagates. One's 8MB $94 and the other 16MB $114. $20 difference. Assuming linearity, people will pay an extra $40 if you say it has 32MB of cache.

http://www.newegg.com/Product/Prod [...] 6822154413
http://www.newegg.com/Product/Prod [...] 6822154414

:) Good posts overall! I hope I'm making a good point.. or two.

Reply to nobly

Quote :

I am somewhat alone in arguing that the
expected failure rate of a RAID 0 with 2 x HDDs
is about the same as a single HDD: using
math, the chance of both HDDs failing
simultaneously is different from the
chance that one or the other will fail.

EITHER WAY, A DRIVE MUST BE REPLACED.

Thus, when a RAID 0 fails, it is practically
equivalent to a single HDD failing, because
one HDD must be replaced, either way,
while in a RAID 0 the second HDD has
most probably NOT failed. See my point?



Don't forget that in RAID-0, when one drive fails, all your data is lost.

Reply to hashv2f16

Quote :

OK, everyone, Elbert is talking about a RAM Disk. Its not a SSD like iRAM, its not really a SSD at all. Its a RAM Disk. Its kind of preselecting what you want to be in system RAM.

@ silverfrog,
No, I'm not talking about searching 512MB on a HDD platter either... Besides, you don't search on a HDD platter - you know the address where it is, so you just drive there. Its a big picture of performance. There is a point where too much cache is more costly than than less cache.

Say the CPU requests data. First the system checks system RAM for it, right? (I assume the CPU wouldn't request data if it was in the CPU's caches). Secondly, if it doesn't find it in system RAM, it asks for it from the HDD.
So first, the HDD searches its cache for the data, right? That's why the cache is there. But if it doesn't find the data, you've lost time searching the cache when you could have been retrieving data.
So:
(average time to get data) = (% of cache hits)*(time to access cache) + (% of cache misses)*(time to retrieve data from disk)

So when the cache does not contain the data, you lose (% of cache hits)*(time to access cache) amount of time. The bigger the cache, the bigger the (time to access cache) is. Once the (time to access cache) = (time to retrieve data from disk), what's the point of having cache? So there is some point where having too much cache is detrimental to performance. Do you see my point?


Its more applicable in the CPU cache/memory subsystems than the HDD, but in principle its similar. Ask why don't we have a 2GB L3 cache? Because to search that 2GB of L3 cache is probably more costly than just going to the system RAM to get the data.

Why don't you think they can have more than 16MB of cache on a HDD now? I'm sure they could throw on 128MB w/o any problems... Perhaps the law of diminishing returns? And if they're just "holding out" on everyone, why aren't 32MB+ caches popping up in mainstream HDDs?



Actually, there is a reason why manufacturers don't include more cache into devices. That reason is cost. 2 GB is L3 cache would be out of everyone's price range. DDR3 RAM or faster is what video card memory is made of and look how much it costs for an extra 256 MB. Hundreds of dollars difference. And, that is cheap compared to cache memory!

L3 Cache memory for a processor is very expensive to add in large quantities. It has nothing to do with diminishing returns. Same goes for Hard drive cache memory. To go from 16 MB to 32 MB is more costly than you think. Like I said, CACHE memory is not your standard DDR400 Ram that you can pick up for $100 for 1 GB sticks.

Secondly, the time it takes to "search" RAM is infinitesimally small compared to how long it takes to access a hard drive platter. The seek time is about 3-5 ms on a hard drive and that's just to find the data, right? Then you have to transfer the data from the disc to cache and finally to system memory. 3-5 millisecond seek time combined with a throughput of roughly 70 MB/sec is incredibly slow compared to the access rate of cache memory, which operates at 400 Mhz+, giving you a speed of 1-2 Gigabytes per second! That is a huge difference. Thus, the whole process goes quicker the more cache memory you have.

Bottom line is:

There are no diminishing returns with cache memory made for hard drives, just like there are no diminshing returns by having more system memory. Memory has address locations which the processor can directly access. There is no "searching". The data is accessed directly and then transferred directly to it's destination, usually to the processor.

The "best" solution is dependent on your perspective. 1 WD Raptor is not the "best" for everyone. People like me who do not CARE about data loss regard 2 or more hard drives in a RAID array as "best". Or, better yet, a solid state hard drive, such as the PCI express RAM card with battery backup. To me, that is "best" because speed is all I care about.

Reply to silverfrog

Acctually 256mb of ddr3 doesn't cost hundreds. More like $80 max.


THIS

Reply to guyinyourattic37
- 0 +

My point was that there is a point where more cache is worse than less cache.

As for the 2GB L2/L3 cache, it was an example to exaggerate my point. I tried to explain that in my previous post. My diminishing returns question was about HDD caches, not L2/L3's...

Yes, I know its more expensive. I know its not system RAM, just like you said. Therefore you cannot compare them like you did:

Quote :

There are no diminishing returns with cache memory made for hard drives, just like there are no diminshing returns by having more system memory. Memory has address locations which the processor can directly access. There is no "searching". The data is accessed directly and then transferred directly to it's destination, usually to the processor.



You must search your cache. Things change in the cache, therefore you either have to have a LUT (look up table) for what is in the cache, or you must search the cache for the data that is requested. Either way is a search. If you want address X, you must search the cache to see if X is there. There is no way to magically know that X is there or not. This is done in hardware so its super fast.
So there are diminishing returns, but only after and beyond you reach a certain cache size.

I know for a HDD it'd take alot of cache to finally bring it to a point where the cache is detrimental to the system. This is what I think you're driving at, and you are correct.

We've kind of highjacked the thread, sorry to the OP.
BTW, I agree w/

Quote :

The "best" solution is dependent on your perspective. 1 WD Raptor is not the "best" for everyone. People like me who do not CARE about data loss regard 2 or more hard drives in a RAID array as "best". Or, better yet, a solid state hard drive, such as the PCI express RAM card with battery backup.

Reply to nobly

Quote :

Acctually 256mb of ddr3 doesn't cost hundreds. More like $80 max.


THIS



You're right. It has come down in price...a little.

Reply to silverfrog
- 0 +

Quote :

My point was that there is a point where more cache is worse than less cache.


Too that point your wrong. The more you have the less you have to depend on a slower media.

Quote :

As for the 2GB L2/L3 cache, it was an example to exaggerate my point. I tried to explain that in my previous post. My diminishing returns question was about HDD caches, not L2/L3's...


Im wanting a 2GB cache L2 or L3 makes no differnce to me.

Quote :

You must search your cache. Things change in the cache, therefore you either have to have a LUT (look up table) for what is in the cache, or you must search the cache for the data that is requested. Either way is a search. If you want address X, you must search the cache to see if X is there. There is no way to magically know that X is there or not. This is done in hardware so its super fast.
So there are diminishing returns, but only after and beyond you reach a certain cache size.


The cache can hold the LUT and much more. The larger the cache size is faster HD and the only diminishing return is on the cost of the HD. The price goes up as the 74Gb raptor shows us and the performance goes up as well due in part to its larger cache.

Quote :

I know for a HDD it'd take alot of cache to finally bring it to a point where the cache is detrimental to the system. This is what I think you're driving at, and you are correct.


No, if you can have more cache your HD will just become all cache or SSD if it cache could ever get that large.

Quote :

Elbert wrote:

Quote:
No, I'm not talking about searching 512MB on a HDD platter either... Besides, you don't search on a HDD platter - you know the address where it is, so you just drive there. Its a big picture of performance. There is a point where too much cache is more costly than than less cache.

I know your not and I said its true that searching 16mb of cache is faster than 512mb cache but its faster to search 512mb of cache than 16mb of cache plus 496mb or hard drive space. Searching cache is timed in the nanosecond and searching HD's are timed in the millisecond thus cache is searched faster.

Again, you do not search HDDs... The head moves to the address given by the master table and you just read from there. I said it before, I'm saying it again. HDD's are done in ms because that is the seek time. Seek time is not search time. Your HDD does 1 seek to drive to a point on the HDD that contains the data. Thats it. It doesn't search the entire drive for your data.


True but with 496mb less cache you have to get all that extra data from the HD.

Quote :

Elbert wrote:

Quote:
Its more applicable in the CPU cache/memory subsystems than the HDD, but in principle its similar. Ask why don't we have a 2GB L3 cache? Because to search that 2GB of L3 cache is probably more costly than just going to the system RAM to get the data.

More cost but not quicker. Cache on the CPU has faster access time than RAM but its a trade of the more cache the less room for other parts of the CPU like ALU. 2Gb of cache would take up alot of the CPU.

That was a rhetorical question... Besides, they can make the CPU as big as they want. (yeah yeah, yields, etc etc, i know.) I was using some exaggeration to make a point. I was giving an example to show my point.


Yes they can but no one could buy it the price would be so high. Your point is wrong for as you step up to faster data storing device, be it a HD the lowest, RAM, or cache the fastest, its always better to have more of the faster storage device.

Quote :

Why does SATA bandwidth limit its worth? Since SATA has versions from 150MB/s to 300MB/s, the burst from the cache could be greater than it is now. Please explain how you got that?

Cost? We're talking about going from 16MB to 32MB of cache... Sure, I can see the cost going up if it was like 512MB or 1GB, but an extra 16MB?? Maybe an extra 20 bucks?
Here's 2 seagates. One's 8MB $94 and the other 16MB $114. $20 difference. Assuming linearity, people will pay an extra $40 if you say it has 32MB of cache.


As you get more and more cache to come closer to the max possible band width. Iram is a perfect example it holds 4Gb's and so how long does it take the Iram to push all 4Gb's throw SATA? System RAM can do it in less than a second and thus my suggest is much faster than IRAM's and a RAID.

Reply to elbert

Quote :

As you get more and more cache to come closer to the max possible band width. Iram is a perfect example it holds 4Gb's and so how long does it take the Iram to push all 4Gb's throw SATA? System RAM can do it in less than a second and thus my suggest is much faster than IRAM's and a RAID.



See, the problem is SATA. When they get I-RAM drives to move to PCI-express, problem solved. PCI express drives would have a maximum speed of 4 GB per second for an X16 card. Either that, or come up with an SATA card that could somehow use two cables (think: SLI SATA).

Reply to silverfrog
- 0 +

Quote :

See, the problem is SATA. When they get I-RAM drives to move to PCI-express, problem solved. PCI express drives would have a maximum speed of 4 GB per second for an X16 card. Either that, or come up with an SATA card that could somehow use two cables (think: SLI SATA).


PCI-express would solve the problem but the reason they dont use it or even the PCI bus the card's pluged into is patent rights. Licensing the rights to run SSD on any PCI, AGP, or PCI Express slot would be high. There is a a SSD PCI card but its cost is high heres the link.
http://www.cenatek.com/product_rocketdrive.cfm

$1600 for a 2Gb SSD is highway robbery.

IRAM is comming with a better solution a SATAII, 300Mb per second, 8Gb SSD but I'm not sure if how much faster than the old IRAM it will be. It could reach 20X speed and may be the best consumer solution. I would want a Drive of system memory due to speed anyway with upwards of 80X that of a HD for my games.

Reply to elbert

lol. Was looking at that Rocket Drive; Retail Price: $1,699.00
Our Price: $1,599.00 You Save $100.00!

lol too funny...save $100! LMAO....

Reply to ShadowdogKGB
1 2
Next
Tom's Hardware > Forum > Storage > Hard Disks > Raid vs raptor
Go to:

There are 1311 identified and unidentified users. To see the list of identified users, Click here.

Please mind

You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.

Add a reply Cancel
Sponsored links
  • Ask the community now
  • Publish
Ad
They won a badge
Join us in greeting them