Storage Solutions Need fastest internal HDD 1TB above

Status
Not open for further replies.
He is correct. With RAID 1 mirrored data, you can read data from both disks in parallel and increase throughput. Only write speeds won't improve. 100khz only needs to load sound files quickly, so read performance will suit him.
P.S. -- What is with your signature about rite? It is hilarious though.
This guy makes all his recommendations based on gaming! In this thread he told 100khz to get a good GPU... for music composition! In another thread he told a photography guy who wants an IPS panel with good colours to get a TN panel.. so he has smoother gaming! :-S
 
He is correct. With RAID 1 mirrored data, you can read data from both disks in parallel and increase throughput. Only write speeds won't improve.

True I agree that the read access times will head South, but due to this 'redundancy' as well as increased reads the overall wear-tear on the drives will also go up, as mentioned here --

Since each member contains a complete copy of the data, and can be addressed independently, ordinary wear-and-tear reliability is raised by the power of the number of self-contained copies.

However, since two identical disks are used and since their usage patterns are also identical, their failures cannot be assumed to be independent. Thus, the probability of losing all data, if the first failed disk is not replaced, may increase.

Since all the data exist in two or more copies, each with its own hardware, the read performance can go up roughly as a linear multiple of the number of copies. That is, a RAID 1 array of two drives can be reading in two different places at the same time, though not all implementations of RAID 1 do this. To maximize performance benefits of RAID 1, independent disk controllers are recommended, one for each disk. Some refer to this practice as splitting or duplexing (for two disk arrays) or multiplexing (for arrays with more than two disks).

When reading, both disks can be accessed independently and requested sectors can be split evenly between the disks. For the usual mirror of two disks, this would, in theory, double the transfer rate when reading. The apparent access time of the array would be half that of a single drive.

HAHAHAHAHAHAHAHAHA!! I do agree on rite, he makes wayward comments that are out of context when viewed from an overall perspective. Never thought about airing it in a signature format though.
 
He made the suggestion only for read performance, not wear and tear.

Still need to keep such stuff in mind, especially when we are considering the amount of data that will be stuck in limbo if the hard-drive(s) decide to take a hike one fine day.

S.M.A.R.T. monitoring will just monitor and tell you, your drive is close to going kaput. It will not prevent the drive from failing OR it cannot magically make it easier to replace the faulty drive / take a back-up / make buying a replacement drive cheap.
 
See, in the real world, we look at what is called IOPS and the ratio between read and write. Considering there would be no budget for a dedicated controller card, and NL SAS/ SAS drives, RAID 1 will suit you better. In my case, RAID 1 helps in better read speeds for multiple Rainbow table - Wikipedia, the free encyclopedia which are several gig's each.

Now, wear and tear doesn't matter on newer drives, even if you run it 24x7, you should be able to get 4+ years without a peep.

got time? read the doc here to get a better idea of how to ideally go about this Analyzing I/O Characteristics and Sizing Storage Systems for SQL Server Database Applications
 
See, in the real world, we look at what is called IOPS and the ratio between read and write. Considering there would be no budget for a dedicated controller card, and NL SAS/ SAS drives, RAID 1 will suit you better.

Now, wear and tear doesn't matter on newer drives, even if you run it 24x7, you should be able to get 4+ years without a peep.

got time? read the doc here to get a better idea of how to ideally go about this Analyzing I/O Characteristics and Sizing Storage Systems for SQL Server Database Applications

Pondering on the point of budget, I realized that even the OP would not like to stretch it beyond ~7000/- considering he buys a 2TB drive. But then implementing RAID 1 will demand he invest upto ~15000/- [for another 2TB drive OR the entire point is moot].

It does considering that internal drives have had their warranty slashed to just ~2 years [from a previous 3 year cap] and Seagate drives just have a measly ~1 year cover. Drives especially Western Digital Green's and Black's have been notoriously unreliable, regularly getting snuffed out like flies.

So let us wait for OP's call. Thanks for the links will make it a point to read it. Cheerio!!
 
First you said RAID 1 is not good for read performance.
Then you said RAID 1 is not reliable.
Buddy please be precise! They are indeed perfect for both the above.
Most disks do not crash prematurely. They die slow deaths with plenty of warning signs through SMART parameters.
Enough time to backup a disk or buy a new one.
And not a risk with a mirrored RAID 1 setup.
Of course implementing RAID 1 depends on budget.
 
First you said RAID 1 is not good for read performance.
Then you said RAID 1 is not reliable.
Buddy please be precise! They are indeed perfect for both the above.

Most disks do not crash prematurely. They die slow deaths with plenty of warning signs through SMART parameters.
Enough time to backup a disk or buy a new one.
And not a risk with a mirrored RAID 1 setup.

Of course implementing RAID 1 depends on budget.

I get it Sire, withdrawing all statements made here. Cheerio!!
 
Status
Not open for further replies.