CougTek said:There were computers before your time?
Tannin said:Bahhh .... They need to stop taking the medication. Seriously, what planet are they on? Seagate had clear, see-through hard drives routinely available to dealers for display purposes years ago. I mean lots of years ago. I forget exactly when they started doing this, possibly before my time, but they were readilily available back around the time that 500 and 850MB drives were the going thing.
My direct and indirect thoughts on the SR review are the following:And I think it's overhypered bullshit for a company that advertises on SR.
Nonesense! A pedestrian Samsung drive fell within 5% of the Raptor in two of SR's own desktop benchmarks. But nary a word on this. No banners unfurrowed, and no band struck up the chorus.As the months rolled by, the Raptor continued to hold its own against the latest SATA and SCSI drives to hit the channel.
A firmware update, and oh look ! - those amazing Raptors are at it again! And this begs the question: if most drives are recieving tweaks along the way, why not pester all manufacturres for new review samples and revisit their performance too? Did the fact that the new Raptor was to appear in a couple of weeks have anything to do with it? Perhaps? Eh? Whats that? The WD galley's drummer has increased the tempo! Bum-bum-bum-bum-bum-bum-bum.....Further, like most drives, the WD740GD has quietly received tweaks and revisions here and there. The latest iteration, the WD740GD-00FLC0, boasts improvements of up to 14% in its single-user scores.
Newsflash -- I certainly never came to that concensus. And I also know a good number of other posters who never exhibited such fallacy in their logic either. In actuality, this is kind of insulting to the posters who hung around and tried to maintain some sort of order and sainity amongst a population infected with the likes of Raid0 mania and NCQitis.As users got their hands on retail drives, however, they quickly noticed that their shiny new hotrods topped out with 57 MB/sec transfer rates rather than the 63 MB/sec that SR's WD-supplied sample boasted. Sequential transfer rates (STR), unfortunately, are the easiest HD performance metric to measure and also the least indicative of how the drive will perform under real-world situations. It was obvious from the lower STR figures that the shipping Raptors incorporated the more conservative zone-layout found in our original sample rather than the one used in the following unit.
Conspiracy theories ensued in the community. Eventually, a flawed consensus was reached: If the shipping Raptors featured the lower transfer rates exhibited in SR's first sample, then the write-caching, firmware, and performance of shipping units must also be similar to that of the first drive's. This logic, of course, is fallacious. Zone configuration (and thus transfer rates) is independent of write caching and firmware.
Really? I thought he viewed us as a bunch of deserters.CityK said:Anyways, as I know he views posts here, I hope he will take what I have to say into consideration.
time said:Instead of benchmarking operations that are already fast and are therefore unnoticed by the user, how about measuring the slower operations that users do notice?
mubs said:I have an 80GB and 120GB WD purchased in 1992 and 1993...
GB. That should have read 2002 and 2003.Merc said:You mean MB, right mubs?
Actually Tannin, I had you in mind when I wrote about the Strawman argument, as I specifically remember you writing something along the lines of "depicting you as a strawman". But there are, no doubt, perhaps several other examples I could have drawn from memory...the fact remains: its pretty easy to blow them down when you line them up yourself.Tannin said:I first raised this point - ths vital, absolutely fundamental point - more years ago than I care to remember. (Not that I'm claiming to have invented it, of course, I was merely one of the more prominent and outspoken participants in the debate.)
Well said.In this vein of practical speed, we should put together a list of SCSI cards and how much of a delay they introduce into the POST sequence. Or which motherboards pass you off to the first boot device sooner. Or how to code firefox to be pre-cached during the startup sequence...