Slashdot Mirror


Intel Stomps Into Flash Memory

jcatcw writes "Intel's first NAND flash memory product, the Z-U130 Value Solid-State Drive, is a challenge to other hardware vendors. Intel claims read rates of 28 MB/sec, write speeds of 20 MB/sec., and capacity of 1GB to 8GB, which is much smaller than products from SanDisk. 'But Intel also touts extreme reliability numbers, saying the Z-U130 has an average mean time between failure of 5 million hours compared with SanDisk, which touts an MTBF of 2 million hours.'"

130 comments

  1. MTBF by Eternauta3k · · Score: 5, Interesting

    'But Intel also touts extreme reliability numbers, saying the Z-U130 has an average mean time between failure of 5 million hours compared with SanDisk, which touts an MTBF of 2 million hours.'"
    Is this hours of use or "real time" hours? I don't know about other people but my pendrives spend most of their time disconnected.
    --
    Yeah. Would you choose a neurosurgeon who pokes around people's brains in his spare time? I wouldn't.
    1. Re:MTBF by stratjakt · · Score: 1

      Think of the caching flash in a hybrid drive.

      And why wouldn't you want your pen drive to last 2 1/2 times longer?

      Would it be that you're an AMD "fan" and are rooting against your home teams rival?

      --
      I don't need no instructions to know how to rock!!!!
    2. Re:MTBF by Reverend528 · · Score: 0

      Did they really test these for 5 million hours or are they just pulling the number out of their ass?

    3. Re:MTBF by eluusive · · Score: 0

      5 000 000 hours = 570.397764 years I don't know how Intel came up with those numbers, but I'd be happy if I lived to see my SanDisk flash keep working at only 2 000 000 hours.

    4. Re:MTBF by textstring · · Score: 1

      Any statisticians on slashdot?

    5. Re:MTBF by omeomi · · Score: 1

      This FAQ seems to suggest that MTBF would imply actual hours of active use:

      http://www.faqs.org/faqs/arch-storage/part2/sectio n-151.html

      There is significant evidence that, in the mechanical area "thing-time" is much more related to activity rate than it is to clock time.

    6. Re:MTBF by Target+Drone · · Score: 3, Insightful

      5 000 000 hours = 570.397764 years I don't know how Intel came up with those numbers

      From the wikipedia article

      Many manufacturers seem to exaggerate the numbers to sell more products (i.e.) Hard Drives to accomplish one of two goals: sell more product or sell for a higher price. A common way that this is done is to define the MTBF as counting only those failures that occur before the expected "wear-out" time of the device. Continuing with the example of hard drives, these devices have a definite wear-out mechanism as their spindle bearings wear down, perhaps limiting the life of the drive to five or ten years (say fifty to a hundred thousand hours). But the stated MTBF is often many hundreds of thousands of hours and only considers those other failures that occur before the expected wear-out of the spindle bearings.
    7. Re:MTBF by hackwrench · · Score: 1

      Where did you get the idea that he didn't want his pen drive to last 2 1/2 times longer? We get lied to so much that it's reasonable to be skeptical. Why are you trying to attribute ulterior motives to his skepticism?

    8. Re:MTBF by Skhaatra · · Score: 1

      When you heat electronic devices they have been proven to fail at a higher rate. The increase in temperature and the increase in failure rate has a known relationship. Therefore you can heat up the equipment when you test it, and that will simulate it being used for a longer period of time. So, for example, you can heat up the flash disks by 50 degrees, then test 100 of them over 2 weeks, and then extrapolate from that what the failure rate would be at room temperature. Hence the ability to state values that a very high. Another way of coming up with an MTBF is based on the MTBF of all the component parts, and how they are connected (with what, in series, in parallel etc), without actually testing the entire flash drive for MTBF. Usually both are used, and any errors in the calculated MTBF is corrected with the actual from testing, which is then corrected with the actual from out in the field due to returned parts. Cheers, Ed.

    9. Re:MTBF by smallfries · · Score: 4, Funny

      Yes of course they tested them for 5 million hours, after all it's only 570 years. Don't you know your ancient history? The legend of Intelia and their flashious memerious from 1437AD?

      --
      Slashdot: where don knuth is an idiot because he cant grasp the awesome power of php
    10. Re:MTBF by Anonymous Coward · · Score: 0

      Mutant Teenage Beastly Fido?

    11. Re:MTBF by dgatwood · · Score: 1

      I am not a product tester, so I can only go with what I've read on the subject, but what you describe just doesn't sound valid to me in general electronics testing.

      First, according to the Google results, thermal considerations had no statistically significant impact on failure rate. Yes, thermal failures can shorten life expectancy (particularly of hard drives), but in a real-world environment, there are far more things besides heat that can cause drive failures, including metal fatigue, bearing fluid leakage, electronics failures (which are not generally thermal in nature), lightning or surges, etc. To raise the temperature and shorten your MTBF testing would be disingenuous to the point that it borders on fraud.

      Also, for solid state hardware with no moving parts, thermal failure is somewhere down around number 100 in the things that cause device failure. My best guess is that the number one cause of flash drive failure is the physical breakage of the traces leading from the USB connector, the number two cause of flash drive failure is other physical stress damage causing board breakage, and the number three cause is idiots putting it in the washing machine, dropping it in the toilet, etc.

      That's not saying that thermal aging testing isn't useful for some products (electrolytic and paper/oil capacitors, plastics, etc.), but you can't realistically expect me to accept reliability statistics based on that alone, especially for silicon and other metal products, where I've read that assumptions of temperature-to-failure-rate correlation are not at all valid.

      Manufacturers of equipment should do thermal testing at temperature extremes to verify that the hardware MTBF does not dramatically change while the temperature is within acceptable limits. That is not the same thing as forging your MTBF numbers by raising the temperature and saying "at 120F, that's equivalent to running it twice as long" or some other such nonsense. Indeed, the very fact that you suggested such a testing procedure is precisely why manufacturers should be required to publish their testing methodology used to determine MTBF so that it can be scrutinized thoroughly and corrected where necessary....

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    12. Re:MTBF by Lehk228 · · Score: 1

      because in 2.5 million hours i , my grandkids, and likely my great grand kids will be dead

      --
      Snowden and Manning are heroes.
    13. Re:MTBF by Anonymous Coward · · Score: 0

      Slightly off topic, but this recalls to me a 1980's ad from some outfit proudly proclaiming that they had the lowest MTBF in the industry.

    14. Re:MTBF by sauron_of_mordor · · Score: 1

      and cd's are indestructable too IIRCC.

    15. Re:MTBF by ajs318 · · Score: 1

      I have been a product tester. And electronic components are more likely to fail at elevated temperatures: 165 degrees is the Kiss of Death for silicon. In practice, if you can't bear to keep your finger on a device (so about 60 degrees, but this is a person-to-person variable), it's probably too hot.

      Certain parts for agricultural and earth-moving vehicles (possibly ordinary cars, too, but we were a bit specialised) have to go through a "burn-in" test. This involves loading special test firmware, which will exercise all the inputs and outputs; then packing them into an oven at 80 degrees, attached to a PSU and load bank, and seeing how they fare over a given time. According to the "bathtub" curve, a unit is most likely to fail in the first few hours or the last few hours of its design lifespan. By stressing them hard, we were able to weed out the duff ones (better they fail in the factory than in the field) and possibly identify process changes that could increase reliability. Of course, the units also had to be re-loaded with the real firmware; but this was done as the first stage in the end-of-line parametric test.

      This procedure was not carried out on all products, but every new design was subjected to fairly extensive validation testing to ensure fitness for purpose. For instance, the ignition sequence controller in a gas boiler must never leave the gas valve open without a flame, except during the ignition timeout while the spark generator is in operation; and no single component failure (or cascade triggered by a single component failure) may shorten the pre-purge timeout (after the fan has been detected as running, but with the gas off to draw fresh air through the firebox) or lengthen the ignition timeout. All this was tested by FMEA (Failure Modes and Effects Analysis -- i.e. thought experiment) and deliberate sabotage; and obviously, validation testing included tests at higher temperatures than would be encountered in the appliance (just below the firebox in a simple up-firing boiler gets into the mid-70s; by contrast, the top of a down-firing condensing boiler near the air intake is fairly cool at 55 degrees, but higher temperatures may be seen under overheat conditions) but end-of-line parametric testing just consisted of running the control through one or more full cycles, possibly at extremes of voltage if the design was inherently susceptible to mains fluctuations, and verifying that operation was within parameters.

      We never made Flash drives; but TTBOMK they are able to withstand a hot wash cycle, immersion in a WC and even an hour's playing-with by a three-year-old.

      --
      Je fume. Tu fumes. Nous fûmes!
  2. Info. by Anonymous Coward · · Score: 2, Informative

    Wear-levelling algorithms. Is there a resource for finding out which algorithms are used by various vendors' flash devices? And links to real algorithms? Hint: not some flimsy pamphlet of a "white paper" by sandisk.

    I want to see how valid the claims are that you can keep writing data on a flash disk for as long as you'll ever need it. Depending on the particular wear-levelling algorithm and the write pattern, this might not be true at all.

    1. Re:Info. by EmbeddedJanitor · · Score: 3, Informative
      These claims will be made at the flash level (ie. ignoring what the block managers and file systems do).

      Different file systems and block managers do different things to code with wear levelling etc. For some file systems (eg. FAT) wear levelling is very important. For some other file systems - particularly those designed to work with NAND flash - wear levelling is not important.

      --
      Engineering is the art of compromise.
    2. Re:Info. by Hal_Porter · · Score: 1

      Do a patent search for wear levelling. M Systems (bought by Sandisk) have lots of very well written patents that describe how they do it. Datalight has some too.

      This paper has a good overview
      http://www.cs.tau.ac.il/~stoledo/Pubs/swste2005.pd f

      Third parties probably either license one of these patents, or violate them ruthlessly if they are based in China - it's not like some no name thumb drive manufacturere in Shenzen is going to be worth investigating, given that all the code is masked into a microcontroller and they are probably immune for lawsuits. Mind you, it's quite possibly that they skip wear levelling completely.

      OTOH you could just write block 0 over and over again from the USB host, and connect a bus analyzer to the NAND interface. You can tell by how the NAND physical address changes which patent they are violating.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
  3. hmm by mastershake_phd · · Score: 2

    read rates of 28 MB/sec

    Shouldn't a solid state device be able to be read faster than a spinning disc?

    1. Re:hmm by Anonymous Coward · · Score: 1, Informative

      Shouldn't a solid state device be able to be read faster than a spinning disc?

      Yes and no.

      With random access the bottleneck is going to be superb - random reads are going to be far faster than any mechanical drive (where waiting for the drive and heads to move) are a real problem.

      With sustained transfers, speeds are going to depend on the interface - which in this case is USB 2.0 - which has a maximum practical transfer rate of... about 30MB/s.

      What's needed are large flash drives with SATA 3 interfaces.

    2. Re:hmm by SatanicPuppy · · Score: 2, Informative

      Not necessarily...Three platters spinning at 7200rpm is a lot of data.

      The place where you make up time with solid state is in seek time...There is no hardware to have to move, so finding non-contiguous data is quicker.

      --
      ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
    3. Re:hmm by Kenja · · Score: 1

      Not realy, the advantage of solid state VS magnetic media is in the seak time not the transfer rate.

      --

      "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
    4. Re:hmm by mastershake_phd · · Score: 1

      Solid state RAM can do GBs per second.

    5. Re:hmm by Joe+The+Dragon · · Score: 1

      The USB bus slows it down firewire 400 is faster.

    6. Re:hmm by dbIII · · Score: 1

      Unfortunately not - which is why the MS virtaul memory on flash should be renamed StupidFetch. Seek times are better and fragmentation is not an issue, so it may be better than a filesystem on a really full disk that has got into a mess over time - but otherwise virtual memory on disk will be dramaticly faster.

  4. Reason to switch #341 by richdun · · Score: 1

    We know Apple commands a great deal of pricing advantage with their current supplier(s) (Samsung, if memory serves). But, could this be another reason to switch, by picking up Intel CPUs and Intel flash memory chips? Cringely could be getting closer to actually being right - if Intel buys Apple, suddenly iPod, iPhone, Mac, etc. production could go in-house for a huge chunk of the parts.

    Just had to throw an Apple reference in there. It's /. law or something.

    1. Re:Reason to switch #341 by natebizu · · Score: 1

      This just in: "Intel buys Apple"
      in another story, "Microsoft buys AMD"

    2. Re:Reason to switch #341 by Anonymous Coward · · Score: 0

      Except that Intel don't make chips that are suitable for the iPod and iPhone anymore.

  5. Ah, good, more competition by rolfwind · · Score: 1

    Maybe in the next few generation, we'll get the best of both worlds, much higher capacities and reliability.

    Need to check out how Intel is actually backing up it's reliability claim - if they just replace the drive when it stops working - that may be a cheap proposition for them (it fails a year or two later, even a currently highend drive by that time the drive is small to relative current numbers and they can replace it with a cheap one). Hate for this to become a war with who can fiddle with the numbers the best while the overall quaility remains the same in reality.

    1. Re:Ah, good, more competition by Anonymous Coward · · Score: 0

      Intel is calculating these reliability numbers using the same metrics as everyone else in the Flash world. The increased performance and reliability numbers are because Intel is using Single Level Cell flash in the SSD, also explaining the lower densities. These are generally the same chips as the upcoming "Robson" Nand caching scheme on the upcoming Santa Rosa chipset. They are increasing the number of dies within the TSOPs (stacking) for SSD drives.

      Intel is selling the MLC flash to Apple (for NANOs) and others, where the cycle count and performance requirements are lower and the premium is on the density.

  6. verification by omnilynx · · Score: 1

    I believe I will wait for third-party verification of those numbers. Specifications from the producers tend to have somewhat... generous fine print.

    --
    ceci n'est pas une .sig
  7. Spinning states by HomelessInLaJolla · · Score: 2, Informative

    These days the platters spin so fast and the data density is so high that the math just might work out the same for a solid state device and the spinning disc--ie. the spinning disc may, mathematically, approximate the solid state device.

    At first thought I agree, though. Maybe there's something inherent in the nature of the conducting materials which creates an asymptote, for conventional technologies, closing in around 30 mb/sec.

    --
    the NPG electrode was replaced with carbon blac
    1. Re:Spinning states by Anonymous Coward · · Score: 1, Funny

      > Maybe there's something inherent in the nature of the conducting materials which creates an asymptote, for conventional technologies, closing in around 30 mb/sec.

      No. That's crazy hobo talk.

    2. Re:Spinning states by Hal_Porter · · Score: 1

      At first thought I agree, though. Maybe there's something inherent in the nature of the conducting materials which creates an asymptote, for conventional technologies, closing in around 30 mb/sec.

      Well, 30 pieces of silver was what Judas got for selling out God. I think the connection is clear.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
  8. Lies, damn lies, and MTBF claims by Anonymous Coward · · Score: 0

    But Intel also touts extreme reliability numbers, saying the Z-U130 has an average mean time between failure of 5 million hours compared with SanDisk, which touts an MTBF of 2 million hours.

    Looks to me like Intel simply has less of an aversion to lying. Remember their old Pentium add which claimed surfing the 'net would be sooooo much faster with their new Pentium, 'cause it's not like it's actually limited by the speed of you network connection?

    1. Re:Lies, damn lies, and MTBF claims by shaitand · · Score: 1

      No but I have seen webpages rendered on a Pentium 1 versus a Pentium III with the same amount of ram and on the same network connection. My guestimate is that about the P2 400mhz w/256mb ram and background processes cleaned up is where the machine doesn't matter and the network connection is the only substantial bottleneck.

      Downloading the content is not the only aspect of browsing the web, the machine must parse and render that content as well.

    2. Re:Lies, damn lies, and MTBF claims by ggy · · Score: 1

      My guestimate is that about the P2 400mhz w/256mb ram and background processes cleaned up is where the machine doesn't matter and the network connection is the only substantial bottleneck.
      And then came MySpace.
  9. WTF? by xantho · · Score: 3, Insightful

    2,000,000 hours = 228 years and 4 months or so. Who the hell cares if you make it to 5,000,000?

    1. Re:WTF? by Kenja · · Score: 4, Insightful
      "2,000,000 hours = 228 years and 4 months or so. Who the hell cares if you make it to 5,000,000?"

      Mean time between failures is not a hard perdiction of when things will break. http://en.wikipedia.org/wiki/MTBF

      --

      "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
    2. Re:WTF? by biocute · · Score: 1

      Well, for those who care about the difference between 250 FPS and 251 FPS in a graphic card.

    3. Re:WTF? by merreborn · · Score: 1

      2,000,000 hours = 228 years and 4 months or so. Who the hell cares if you make it to 5,000,000?


      MTBF doesn't work like that. You can, however, directly translate it to a likelyhood of failure over a year; that is, if a 1 million hour MTBF corresponds to a 1% chance of failure over the course of a year, then a 5 million hour MTBF corresponds to an even lower likelyhood of failure over the course of a year.
    4. Re:WTF? by vertinox · · Score: 1

      MTBF is an average. So things don't automatically break at after 2 million nor do all of them last till then.

      The higher the number, the statically less you'll likely get hit with a drive failure.

      Think of it like getting in a car accident in the country road versus getting in a car accident in the busy city. You might go your entire life in both places never getting in an accident, but in both places you always have the possibility you will wreck on your first day of driving.

      However, you fare much better on the country road for your insurance rates because statistically you will get in less accidents than you do if you lived in the city.

      --
      "I am the king of the Romans, and am superior to rules of grammar!"
      -Sigismund, Holy Roman Emperor (1368-1437)
    5. Re:WTF? by Anonymous Coward · · Score: 0

      You can, however, directly translate it to a likelyhood of failure over a year;

      Unless there's some surprising statistical theorem that I've somehow missed involved here, you can only do that if you assume that failure is equally for any year n in which the device has not already failed. Given that this seems unlikely, I'd think that you can not translate it directly to a likelihood of failure over a given year. (It might be a useful statistic anyway, though!)
    6. Re:WTF? by oddaddresstrap · · Score: 1

      Mean time between failures is not a hard perdiction of when things will break.

      True, but since it supposed to be the average time between failures, it had better be closer to 228 than, say, 5 most of the time or the use of the statistic as a selling point is utterly bogus (some would say fraudulent). It would help to know what the (guesstimated) standard deviation is. The implication of a MTBF of 2x10^6 hours is that it will easily outlast you.

    7. Re:WTF? by SeaFox · · Score: 1

      Mean time between failures is not a hard perdiction of when things will break.

      True, but even if the drive lasts half as long as the manufacturer's MTBF claim, your data will still outlive you.
      .
      .
      . ...wow, why do I feel the urge to say that with a Russian accent.

  10. Why? what does it matter by WindBourne · · Score: 0

    2 million hours vs 5 million hours. There are ~10K hours in a year. With 2 million hours, there is more than 200 years. If you are still using the same computer in 200 years, I will be either impressed or scared.

    --
    I prefer the "u" in honour as it seems to be missing these days.
    1. Re:Why? what does it matter by 26199 · · Score: 1

      It matters a lot if you're using 200 of them at your company...

    2. Re:Why? what does it matter by Jarjarthejedi · · Score: 2, Informative

      MTBF matters because it's random. They're not saying that every drive will last that long, they're saying that the average drive will. Therefore the chance of any drive failing within a reasonable amount of time drops the more the mean time is. So with a 5000000 MTBF the chance of any one drive failing in your life time is incredibly minuscule.

      --
      There are two kinds of fool One says 'This is old therefore good' Another says 'This is new therefore better'- Dean Ing
    3. Re:Why? what does it matter by omarques · · Score: 0

      (...)in 200 years, I will be either impressed or scared.
      Really? I will be dead.

    4. Re:Why? what does it matter by twiddlingbits · · Score: 1

      2 Million hours MTBF means the time to a failure is a lot longer than my lifetime too. Overkill isn't always better.

    5. Re:Why? what does it matter by Reason58 · · Score: 5, Funny

      MTBF matters because it's random. They're not saying that every drive will last that long, they're saying that the average drive will. Therefore the chance of any drive failing within a reasonable amount of time drops the more the mean time is. So with a 5000000 MTBF the chance of any one drive failing in your life time is incredibly minuscule. In 20 years from now, when hard drive capacity is measured in yottabytes, will you really be carrying around a 512MB thumbdrive you bought for $20 back before the Great War of 2010?
    6. Re:Why? what does it matter by jrumney · · Score: 1

      MTBF matters because it's random. They're not saying that every drive will last that long, they're saying that the average drive will.

      False advertising is illegal in many countries. This 5 million hours figure (and SanDisk's 2 million) seems to be based on much shorter tests of large numbers of devices and extrapolating the results based on the assumption that this randomness is evenly distributed. They MUST know that this assumption is wrong. As taught in basic engineering courses, failure distributions are basically U shaped, with most failures on the steep left hand side being detected during manufacture (and hence not counted in their MTBF figures), and those on the right hand side optimally starting to increase shortly after the warrantee expires by fine tuning the manufacturing process to minimise production costs and maximise unit sales.

    7. Re:Why? what does it matter by LoudMusic · · Score: 2, Insightful

      In 20 years from now, when hard drive capacity is measured in yottabytes, will you really be carrying around a 512MB thumbdrive you bought for $20 back before the Great War of 2010? How do you know it's going to happen in 2010? Are you SURE it's going to happen in 2010? That only gives me 3 years to prepare the shelter ...
      --
      No sig for you. YOU GET NO SIG!
    8. Re:Why? what does it matter by LordSnooty · · Score: 1

      No, more hours can be good - just think, you can pass down your Family Photo Thumbdrive to your kids, who might be able to pass it onto their grandkids, if USB is still available...

    9. Re:Why? what does it matter by Surt · · Score: 0, Flamebait

      Barring Bush declaring the constitution revoked, you probably ought to bet on the great war starting before his term in office expires. That gives you even less time to prepare the shelter.

      The odds of the next president being an outspoken war proponent are very low.

      --
      "Who is the Journal of Quantum Physics going to believe?" --Stephen Hawking
    10. Re:Why? what does it matter by dgatwood · · Score: 1

      So with a 5000000 MTBF the chance of any one drive failing in your life time is incredibly minuscule.

      I have a box full of dead hard drives that would disagree with you, and I didn't typically use lots of drives at once until fairly recently, so most of those failures were consecutive single drive failures....

      The numbers are utterly meaningless for individual consumers. They are only really useful at a corporate IT level with dozens or hundreds of drives to figure out how many spares you should keep on hand. Beyond that, they're just B.S. marketing drivel to try to make you believe that their drives are better, and thus keep buying them even after your last eight drives crashed.... And honestly, I wouldn be surprised if the numbers were even in the ballpark for large numbers of drives, judging from the failures I've seen over the years. My experience has been that particular models of drives either work nearly forever or die repeatedly, and there's not much in-between.... :-)

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    11. Re:Why? what does it matter by revolu7ion · · Score: 1

      In 20 years from now, when hard drive capacity is measured in yottabytes, will you really be carrying around a 512MB thumbdrive you bought for $20 back before the Great War of 2010?
      Sorry to rain on your future war, but great war has already been taken (1914-1918).

      I suggest: "the Google-net war of 2010" after Google becomes self aware (of adwords)
      --
      Jesus Saves
    12. Re:Why? what does it matter by cheater512 · · Score: 1

      By then it'll be like keeping a 5.25' disk. Sure I still have 3 drives lying around but I wouldnt dream of using them.

    13. Re:Why? what does it matter by x2A · · Score: 1

      1914-1918 was a pretty good war, but I wouldn't go as far as to say it was great. The storyline was pretty weak, especially the beginning, and the effects left a lot to be desired. Hardly any of it was even in colour, and yeah I know black and white's supposed to be all "artsy" but I'd say it's more pretentious.

      --
      The revolution will not be televised... but it will have a page on Wikipedia
  11. Sounds familiar by stokessd · · Score: 1

    8 GB should to be enough for anybody...

    1. Re:Sounds familiar by Joe+The+Dragon · · Score: 1

      Not vista users as M$ wants you to have 15GB

  12. 2 million hours? by jgoemat · · Score: 2, Insightful

    So on average, it will last 570 years instead of 228?

    1. Re:2 million hours? by Anonymous Coward · · Score: 0

      Yes. And unless the standard deviation is 0, almost no actual samples will last exactly 570 years. And knowing MTBF says almost nothing useful to you.

  13. Warning by EmbeddedJanitor · · Score: 1
    The MTBF only applies to failures at ther NAND level, not the software level.

    In most cases the part that fails is the software, not the hardware. For example, FAT is a terrible way to store data you love. To get reliability you need to use a flash file system that is designed to cope with NAND.

    --
    Engineering is the art of compromise.
  14. Failures by syntap · · Score: 1

    But Intel also touts extreme reliability numbers, saying the Z-U130 has an average mean time between failure of 5 million hours compared with SanDisk, which touts an MTBF of 2 million hours.'

    Yes, because I should be concerned that my pr0n collection isn't making it all the way to my laptop for traveling purposes.

  15. Doubtful. by Kadin2048 · · Score: 0

    Did they really test these for 5 million hours or are they just pulling the number out of their ass?

    Well, given that 5 million hours is equal to 570.39 years, I'm going to guess that no, they didn't actually test them for that long.

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  16. Better than FAT. by Kadin2048 · · Score: 2, Interesting

    To get reliability you need to use a flash file system that is designed to cope with NAND.

    Any suggestions of possible candidate filesystems?

    Right now, most people that I know of, use flashdrives to move data from one computer to another, in many cases across operating systems or even architectures, so FAT is used less for technical reasons than because it's probably the most widely-understood filesystem: you can read and write it on Windows, Macintosh, Linux, BSD, and most commercial UNIXes.

    However, a disk that was going to be installed in a single machine could be more flexible; it would be somewhat more acceptable to use a specialized filesystem there (as long as the filesystem wasn't so specific as to make recovery impossible), particularly if you wanted to maximize reliability.

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    1. Re:Better than FAT. by GreyWolf3000 · · Score: 1

      YaFFS2

      --
      Slashdot: Where people pretend to be twice as smart as they really are by behaving like children.
    2. Re:Better than FAT. by Intron · · Score: 1

      I was going to suggest ReiserFS, but I heard it had some mortality problems.

      --
      Intron: the portion of DNA which expresses nothing useful.
    3. Re:Better than FAT. by Anonymous Coward · · Score: 0

      You really don't want to murder your flash drive, no matter how mad you are at it.

  17. Apple would lose all its value over time by rolfwind · · Score: 2, Insightful

    Right now, Apple has 90% of its value due to the vision of Steve Jobs and the products he helps create. This is not to say that there aren't many people involved in Apple's success nor that he even thinks up of most of the products like iPod - but he does a great job in realizing those products and positioning them in the marketplace.

    Unless Intel can keep Jobs and gives him free reign, Apple would soon go rotten from a mediocre vision of someone who just doesn't get the Apple culture and is looking at the spreadsheets when doing products and releasing "Me Too!" items that look and act like everyone elses. Just look at the stagnation of Apple throughout the late 80's and 90's. Intel certainly isn't that company.

    And I think Jobs is too much of a control freak to voluntarily hand himself over to some corporate masters just for a few dollars better margin on a few components.

  18. MEAN time between failures, what does that MEAN by tepples · · Score: 3, Informative

    Did they really test these for 5 million hours or are they just pulling the number out of their ass? It's a mean time between failures. An MTBF figure of 5 million hours means they tested 500,000 of them for 300 hours, and 30 of them failed. A rate of 150 million unit hours per 30 failures equals 5 million unit hours per failure.
    1. Re:MEAN time between failures, what does that MEAN by hackwrench · · Score: 2, Insightful

      That makes about as much sense as declaring that they tested 5 million of them for 1 hour and only one of them failed.

    2. Re:MEAN time between failures, what does that MEAN by tepples · · Score: 1

      That makes about as much sense as declaring that they tested 5 million of them for 1 hour and only one of them failed. Which is, in fact, equally valid. The MTBF for such a test session would be the same: 5 million unit hours.
    3. Re:MEAN time between failures, what does that MEAN by mr_mischief · · Score: 1

      IANA product tester.

      It would be mathematically equal, but I'm not sure it'd be equally _valid_. Given the initial defects and the possibility of misdesign causing heat-related losses or such, some stretch of time is really necessary. Testing 5 million for one hour proves little more than that the expected life is longer than one hour. Testing 200,000 for 25 hours would likely, despite the smaller but still sizable sample size, mean much more. Testing 20,000 at 250 hours would likely mean more still.

      5,000 units at 1000 hours (41 days) or 10,000 units at 500 hours seems much more likely. After all, why make hundreds of thousands of something you're not sure are going to work at all?

    4. Re:MEAN time between failures, what does that MEAN by dgatwood · · Score: 2, Insightful

      Or, depending on how you look at it, they are both equally invalid if, in fact, the products have a thermal failure in which a trace on the board melts with a period of 2 hours +/- 1 hour and you've just started hitting the failures when testing concludes. The shorter the testing time, the more thoroughly meaningless the results, because in the real world, most products do not fail randomly; they fail because of a flaw. And in cases where you have a flaw, failures tend to show clusters of failures at a particular age or level of use. For example, I find that the MTBF for cars and hard drives tends to be the duration of the warranty period plus 1-4 weeks. :-)

      MTBF is approximately useless unless product failures are distributed with a gaussian distribution around the mean. You could have a long tail with a few of them lasting a decade and most of them dying after a week and still have a MTBF figure measured in years, depending on how the testing was done, and specifically on whether they reached the magic cluster death point during the testing period or not. The odds of accidentally hitting such a degenerate case on a single drive are small, but they add up quickly when you're talking about an entire industry worth of drive models. Were that not the case, a whole lot of really awful hard drive models would never have made it out of testing, IMHO.

      I wish manufacturers would be more transparent about their testing methodologies. My gut feeling, though, is that many of them have poor practices and don't want the world to know. This is one of the rare cases where the "if you have nothing to hide, you shouldn't keep this information private" argument actually holds some weight, IMHO---this and crypto research. :-)

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    5. Re:MEAN time between failures, what does that MEAN by jelle · · Score: 1

      The main problem is that manufacturers loudly blare the MTBF/MTTF values without telling people how long the test was done, hence they can use whatever time they like. You have to agree in the very least that even for comparison between products from different manufacturers, the MTBF is useless, for the simple fact that one manufacturer might test for 100 hours, and the other for 1000 hours...

      As such an unreliable measure, the first two letter 'MTBF' stands for 'misleading'.

      I didn't just say it, Carnegie Mellon University examined reliability and found 'MTBF' doesn't mean much:

      http://www.usenix.org/events/fast07/tech/schroeder /schroeder_html/index.html

      --
      --- Hindsight is 20/20, but walking backwards is not the answer.
    6. Re:MEAN time between failures, what does that MEAN by mr_mischief · · Score: 1

      Oh, there's no doubt there's some serious issues with the numbers and how they're calculated. An industry standard for minimum number of units tested and minimum number of hours tested would be nice. At least disclosure of the testing conditions should be a minimum.

      I'd like to see the industry do it without getting government involved. A simple law that clearly states that the manufacturers must describe the testing procedure in order to use the number for marketing would be great if the industry doesn't do it on its own. Of course, in the US there's never a simple law passed on one topic because it's good for the people. They always play politics with pork barrel projects, social issues, and such that they roll into one huge bill. Upon voting for or against said bill, one politician will get attacked in that it's bad for the environment while another will get attacked that it's bad for fiscal policy. One will defend his vote because it's good for small business and the other because it's good for "the poor" or "the arts", both without specifying who that is and how it actually helps. So yeah, it'd be nice if the industry could come up with a standard.

    7. Re:MEAN time between failures, what does that MEAN by DriveDog · · Score: 1

      Yeah, I was just thinking that an MTBF is pretty meaningless without knowing the type of distribution and the variance, and even the skew. If a few would last a billion years, then a bunch would fail really soon.

  19. Wear leveling in hardware by tepples · · Score: 1

    For example, FAT is a terrible way to store data you love. To get reliability you need to use a flash file system that is designed to cope with NAND. Or you could create a FAT partition inside a file, stick that file on a flash file system, and mount the FAT partition on loopback. The microcontrollers built into common CF and SD memory cards do exactly this, and this is why you only get 256 million bytes out of your 256 MiB flash card: the extra 4.8% is used for wear leveling, especially of sectors containing the FAT and directories.
    1. Re:Wear leveling in hardware by EmbeddedJanitor · · Score: 3, Interesting
      The cards with internal controllers do something like you say and you can thead the SD or SmartMedia specs for details. They manage a "free pool" primarily as a way to address bad blocks, but this also provides a degree of wear levelling.

      Putting a FAT partition onto such a device, or into a file via loop mounting, only gives you wear levelling. It does not buy you integrity. If you eject a FAT file system before mounting it then you are likely to damage the file system (potentially killing all the files in the partition). This might be correctable via a fschk.

      Proper flash file systems are designed to be safe from bad unmounts. THese tend to be log structured (eg. YAFFS and JFFS2). Sure, you might lose the data that was in flight, but you should not lose other files. That's why most embedded systems don't use FAT for critical files and only use it where FAT-ness is important (eg. data transfer to a PC).

      --
      Engineering is the art of compromise.
  20. 5 million hours MTBF by Dachannien · · Score: 2, Insightful

    That figure doesn't tell me jack. What I want to know is if I order 100 of these things, how many of them will fail just after the warranty expires?

    1. Re:5 million hours MTBF by 2nd+Post! · · Score: 1

      Half as many as if you had bought from SanDisk?

    2. Re:5 million hours MTBF by Dachannien · · Score: 1

      Who can tell? Maybe half of them fail five minutes after you first plug it in, and the other half fail ten million hours later. Maybe only a very few fail within the first five years, and the failures start picking up after that. Nobody can tell from this figure, which is pure marketroid-speak without any practical application.

  21. Yeah, if you RAID them by tepples · · Score: 1

    Shouldn't a solid state device be able to be read faster than a spinning disc? Yes. You could fit a RAID of twenty miniSD cards into an enclosure smaller than a laptop hard drive. Panasonic P2 memory cards work this way. However, Intel sells flash chips and must quote the specifications for individual chips.
  22. Hard drive heads aren't used in parallel by tepples · · Score: 1

    Not necessarily...Three platters spinning at 7200rpm is a lot of data. Due to limitations in the accuracy at which a servo can position a hard drive's read and write heads, a hard drive reads and writes only one platter at a time. But you're still right that 7200 RPM at modern data densities is still a buttload of data flying under a head at once.
    1. Re:Hard drive heads aren't used in parallel by dgatwood · · Score: 1

      That's true, but a seek to read the same track on the next platter should be very quick, as IIRC, a lot of drive mechanisms do short seeks in a way that significantly reduces the settle time needed compared with long seeks.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    2. Re:Hard drive heads aren't used in parallel by Lehk228 · · Score: 1

      is that a metric or english buttload. also is it bese 2 or base 10?

      --
      Snowden and Manning are heroes.
    3. Re:Hard drive heads aren't used in parallel by amorsen · · Score: 1

      That's true, but a seek to read the same track on the next platter should be very quick

      On some disks the track-to-track seek time for a single platter is shorter than the time to switch to the next platter. Switching platter means you need to find the track again, and you don't know how far you're off to start with. Switching track on the same platter is sometimes easier, because you know exactly how far you are going.

      --
      Finally! A year of moderation! Ready for 2019?
  23. Intel will never buy Apple by sjbe · · Score: 1

    if Intel buys Apple


    It's fun to ponder and an interesting combination but it will never happen unless both the management of Apple and Intel both suffer severe brain aneurysms. Why? Culture and the difficulties of vertical integration. Also, if you want to see the dangers of vertical integration, look no further than Sun and SGI. If you are really big like IBM it's possible to be a soup to nuts vendor but even then it is rare. IBM after all just got out of the PC business which is Apple's core market. It's just really hard for management to competently deliver every aspect of the product. It's not impossible but it is really really really hard.

    Regarding culture, Intel has a notoriously combative culture. Intel's products are generally high quality but they aren't consumer products. Intel doesn't have consumer DNA in them really. Their products are for vendors and techies. Kind of like Nutra-sweet, they've mastered the "branded ingredient" strategy (i.e. "Intel Inside" and Centrino) but they don't really sell to consumers directly. You don't buy an Intel PC, you buy a Dell or HP with "Intel Inside". Apple conversely is one of the best at designing elegant consumer products but doesn't really work deeply with other vendors since most of their sales are to consumers. If Apple had to work with other computer vendors in a big way in all likelihood most of the magic of their products would be lost. Both companies have engineers, salespeople, marketing, and company structures to support these VERY different strategies. It would be a herculean task to make the two companies work well together.
  24. Was that supposed to be a pun? by thelenm · · Score: 1

    Sheesh, I read the headline and thought Intel had developed some buggy chip that somehow stomps on flash memory. Nice, well, at least it got my attention.

    --
    Use Ctrl-C instead of ESC in Vim!
  25. Incremental layout and web accelerator by tepples · · Score: 2, Informative

    Remember their old Pentium add which claimed surfing the 'net would be sooooo much faster with their new Pentium, 'cause it's not like it's actually limited by the speed of you network connection? It wasn't entirely false advertising. A web browser on a faster computer can run more iterations of the incremental layout code, so that the data looks like it's coming in faster. A faster computer can run more complex text and mark-up compression in human-acceptable time, allowing for "web accelerator" software that became especially popular during the wane of dial-up.
  26. For how long? by EmbeddedJanitor · · Score: 2, Interesting
    Intel is a weird company when it comes to the way they do business and I am suprised they are stepping into NAND flash space. The writing was on the wall since they are members of ONFI http://www.onfi.org/

    Intel bough the StrongARM off Digital, then sold it, presumably to focus on "core business" of x86 etc. They've done similar moves with their 8051 and USB parts. It is hard to see what would attract them to NAND flash which has very low margins. NAND flash now costs less than 1 cent per MByte, about a fifth or so of what it cost a year back, and there seems to be no slowing.

    Intel seems to work well with high margin devices (Pentium etc) and not so well with low margin parts (USB chipsets, PXAxxx etc).It is hard to see Intel keeping in the NAND business for very long.

    --
    Engineering is the art of compromise.
    1. Re:For how long? by default+luser · · Score: 1

      Intel has been trying to diversify over the past two decades. Some of their attempts have been fruitful (their move into NOR flash in the late 80s, the move into networking products), whereas others have been mistakes (StrongARM / XScale, LCoS).

      A quick note: Intel is not new to flash memory production. Intel pioneered flash memory production back in the 1980s, and it has been hugely profitable. The new thing here is NAND flash production.

      Both AMD (now Spansion) and Intel jumped on the NOR flash train because, back in the 80s and 90s the run-in-place simplicity made NOR flash a big seller. Now that consumer products demand higher capacity, and the performance issues of NAND have largely been solved (or hidden), NOR flash sales are declining while NAND sales are skyrocketing. Even cell phones have started using NAND memory, which is really hurting NOR flash sales.

      Spansion saw this trend, and attempted to bridge the gap by attaching a NAND chip to a NOR interface (ORNAND), giving cellphone makers the best of both worlds. But so far, the results have been unimpressive (1 Gbit chip capacities). In light of the obvious industry transition, Intel feels they need to move to NAND in in order to remain competitive. Instead of taking the risk of reinventing the wheel like Spansion, Intel has chosen to follow the rest of the industry.

      --

      Man is the animal that laughs.
      And occasionally whores for Karma.

  27. Useful Size by SilentDissonance · · Score: 1

    I'd like to see a semi-affordable (around $250) solid state storage device in a standard form factor and connection (3.5" SATA), at a decent size (15GiB).

    This would be an ideal boot and OS drive for me. / and most of it's directories, along with a decent sized swap (2-3 GiB). Put /home and /tmp on a 'normal' large drive (standard SATA drive of decent speed, RAID array, etc.).

    I've thought about doing this for a while, in fact... but every time I research it out I either come to dead ends with no price info, high prices, or odd interface requirements that aren't suitable for a desktop machine.

    1. Re:Useful Size by maxume · · Score: 1
      --
      Nerd rage is the funniest rage.
    2. Re:Useful Size by b1scuit · · Score: 1

      It would be wiser to put the swap partition on the conventional disks. And for the love of god, buy some RAM. (or quit wasting all that disk space) 2-3GB of swap is silly, and if you actually find yourself using that much swap, you really need more RAM.

    3. Re:Useful Size by networkBoy · · Score: 1

      I'm looking for a Compact Flash to 2.5" style IDE connector myself for basically the same use. I figure I could deal with an 8 Gig / partition, and would just double face tape the CF card to the drive sled.
      -nB

      --
      whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
    4. Re:Useful Size by petermgreen · · Score: 1
      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    5. Re:Useful Size by toddestan · · Score: 1

      Why not RAID0 two 8GB compact flash cards? You would end up with 16GB of fast flash storage with a convienent interface, and I don't think it would be any less reliable than a single mechanical HDD.

    6. Re:Useful Size by blackicye · · Score: 1

      There is one possibility, but its not cheap, and tops out at 4GB (you have to slot in DDR DIMM Modules)
      If you really wanted to and could afford it, you could pick up a few and RAID them.

      Gigabyte's I-Ram

    7. Re:Useful Size by networkBoy · · Score: 1

      Find me a notebook with space inside for 2 hdds (without taking away the cd-rom drive) and with RAID ability...
      -nB

      --
      whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
    8. Re:Useful Size by networkBoy · · Score: 1

      You sir are awesome. Damn expensive though...
      -nB

      --
      whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
    9. Re:Useful Size by toddestan · · Score: 1

      Along the same lines, Hypersonic PC also sells dual HDD/RAID laptops. They are large, and the battery life is short, but it might be just what you need.

      On the other hand, given that a CF card is smaller than a laptop harddrive, and many laptop PATA controllers seem fully functional in the sense that they'll support both a master and slave drive, I wonder if you could hack two CF cards to fit into a regular laptop where the harddrive would usually fit, and then use software raid? (though I imagine you would lose a lot of the speed benefits doing that)

  28. Has anyone actually done the math on this? by Whuffo · · Score: 1
    Let's see now - 2 million hours works out to about 228 years. Seems like a safe claim to make...

    So Intel upping the rating to 5 million hours is meaningless. Somehow I suspect that the people at Intel know this...

  29. Wait a minute.. by aero2600-5 · · Score: 2, Informative

    "mean time between failure of 5 million hours"

    Didn't we just recently learn that they're pulling these numbers out of their arse, and that they're essentially useless?

    Disk failures in the real world: What does an MTTF of 1,000,000 hours mean to you?

    This was covered on Slashdot already.

    If you're going to read Slashdot, at least fucking read it.

    Aero

    --
    Please stop hurting America -- Jon Stewart
    1. Re:Wait a minute.. by greg1104 · · Score: 1

      This was covered on Slashdot already. If you're going to read Slashdot, at least fucking read it.

      Maybe they were waiting until that story was accepted to Slashdot a second time before reading it.

    2. Re:Wait a minute.. by Anonymous Coward · · Score: 0

      Yeah, if you're going to post a story on Slashdot, be sure to have read and internalized the implications of every Slashdot story posted, ever, and not make any passing references to metrics completely, directly relevant to the story but which might be of questionable predictive value. Or be prepared to be condescended to by aero2600-5. Sheesh.

      -TUAC

  30. Seemed Inevitable... by evilviper · · Score: 1

    It seemed pretty inevitable to me, that the Intel/IBM/AMDs of the world would branch out.

    The generation-old fabs they abandon for CPU-making, are still a generation newer than what most anyone else has available. Repurposing those fabs to produce something like Flash chips, chipsets, etc. seems a pretty straight-forward and inexpensive way to keep making money on largely worthless facilities, even after the cost of retooling is taken into account.

    Though they obviously haven't done it yet, companies like Intel have the manufacturing capabilities to leapfrog past all current Flash manufacturers, as far as density is concerned (though, personally, I'd say Flash density is fine, if the price can be driven down).

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    1. Re:Seemed Inevitable... by daverabbitz · · Score: 1

      Intel have been making Flash for years (decades?). And their fabs aren't much if any better (in terms of scale) than those of Altera and Xilinx and probably Kingston, Samsung, Motorola and the rest.

      You do know that 65nM FPGA's were on the market before 65nM processors. The reason is obvious, while Intal has to tool and tune a very complicated CPU to get decent yields, all a RAM/Flash/FPGA manufacturer has to do is tune the small amount of cookie cutter design, and ramp up production. As Ram/Flash/FPGA chips are very homogenous, the design is simpler and it is a lot easier to implement fusing to increase yields (at the expense of density).

      What is new here is that they are selling a consumer flash (S)ATA device.

      --
      What could be better than a jet powered motorcycle? http://www.youtube.com/watch?v=u8l6GTHLSWE
    2. Re:Seemed Inevitable... by Anonymous Coward · · Score: 0

      I work in the research department of one of the large semiconductor manufacturers you refer to. And I can say that you're basically talking out your ass. That's right. You have no idea wtf you are talking about.

    3. Re:Seemed Inevitable... by evilviper · · Score: 1

      You do know that 65nM FPGA's were on the market before 65nM processors.

      No, actually what I know is that you're absolutely wrong.

      Intel's 65nm Core CPUs were released January 2006, while Xilinx was turning out press releases at the end of May 2006, claiming to have produced the first 65nm FPGAs.

      The reason is obvious,

      What appears to be "obvious" to you, is utterly and completely wrong to the rest of the world...

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  31. MTTF != MTBF by MrR0p3r · · Score: 1

    MTTF is not MTBF. In the world of metrics, they're different. While they both measure failures, time to fail and time between failures are different measurements for a reason, they tell us different things about the product we're testing.

    --
    Whatever man, I spelled it write!
    1. Re:MTTF != MTBF by toddestan · · Score: 1

      MTTF is not MTBF. In the world of metrics, they're different. While they both measure failures, time to fail and time between failures are different measurements for a reason, they tell us different things about the product we're testing.

      They are essentially the same for many pieces of computer hardware, since things like a disk drive or a flash chip generally aren't repaired when they fail. Which means that the MTTF is the same as the MTBF, as the first failure is the only failure of the device, as it is then replaced.

  32. High MTBF = Don't you worry about the MTBF. by Skhaatra · · Score: 1

    With such a high figure what they are really saying is that there isn't much to break in there, unless you shove it in a fire or run over it with your car. So don't you worry about it.

    Usually the MTBF will follow a bell curve (measured) and so there are bound to be a few failures within the warranty period due to manufacturing defects, but they should be small.

    If you want to get paranoid about it you could always buy two of them and keep them contents in sync, then at least your MTTR (Mean Time To Repair) will be lower. Note that even with two of them the MTBF remains the same, so either one is still just as likely to fail, but you get time to get a replacement with no down time or loss of data.

  33. Intel vs AMD by bernywork · · Score: 1

    Just wondering, doesn't AMD make a whole bunch of money on Flash memory?

    I know that they spun off the division to Spansion, which was a joint venture with Fujitsu, but if memory serves me correctly they still own a good section (40% or similar) of the company and make a lot of money out of it.

    Conspiracy theories'R'us I guess. It could just be that Intel turned around and said "What do you mean AMD is making a heap of cash out of something that isn't as hard to make as CPUs and we aren't?"

    --
    Curiosity was framed; ignorance killed the cat. -- Author unknown
  34. Such praise for Intel... by Anonymous Coward · · Score: 0

    I'm cautious in reading articles having to do with Intel on slashdot, now that they are sponsored by Intel and have an entire "Opinion Center" for Intel.

  35. What does it "mean" anyway? by obeythefist · · Score: 1

    Rudimentary statistics (IANAS)

    The mean just tells us what you have if you get a sample and divide the sum of values in the sample by the sample size. It's one of the three more meaningful "averages" you can get in statistics. I'd be at least as interested in this case in seeing the mode and median.

    You can "screw up" a mean by adding one or two samples that are extreme. These disks, say they have a 5 million MTBF as the figure you want, but they all really fail after 5 minutes of use. Problem, right? Wrong! You just get a a few units that are good for 1 or 2 billion years and throw them into the mix. Then your mean value skyrockets into millions! The median or mode averages won't suffer from the same distortion.

    Of course if we are dealing with a reasonable, wishfully thinking a normally distributed sample, then of course I would like to know the variance and standard deviation for the sample. This will tell us if all the drives plug away for exactly 5 million years, or if they are just as likely to last 1 million years or 9 million years, or anywhere inbetween or even outside of that.

    But all that extra information isn't provided to us. We just get the mean. On its own, mean doesn't mean much at all.

    --
    I am government man, come from the government. The government has sent me. -- G.I.R.
  36. Remember the not so distant past... by soul_cmd · · Score: 1

    Where these numbers were smashed?

  37. Re:o yeah? by Anonymous Coward · · Score: 0

    A product won't fail if it is never used.

  38. i'll say... by Khyber · · Score: 1

    I would assume hours of use. If you run windows, when you go idle, something's accessing that hard drive (as evidenced by the little blinking light attached to the HDD activity light,) an slowly killing away your read/write cycles. OT: If anyone knows how to stop XP from doing that, please let me know. When everything's gone, only 21 processes are running. What in the hel is accessing my hard drive, I don't know. BOT: As it stands, I'll not really expect this to last very long. If they used the PRAM technology mentioned a few days ago, those 5 million hours of real-time constant use might be a decent estimate. NAND, I'm not so up on the technical specs, so I can't quite give an accurate comparison at this moment.

    --
    Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    1. Re:i'll say... by x2A · · Score: 1

      Disable event logging, and disable swap (you'll need enough real memory for this). OSs will tend to write least often accessed pages to disk, even if there's no memory shortage, so that if memory is needed at some point, it can just quickly free that page and use it, without having to wait to swap it out to disk first. There's also last-accessed-time updates to files/folders that are read, even if they are cached, the writeback of the new time has to occure at some point (i believe this can be disabled in windows - google for it).

      --
      The revolution will not be televised... but it will have a page on Wikipedia
  39. This misses the point by LINM · · Score: 1

    It's going to come down to cost. The size is just the market segment they are starting off in.

    --

    Hunger is the best sauce.

  40. WTF is up with these MTBF numbers? by Anonymous Coward · · Score: 0
    Come on. If there's a reported 5e+6 hrs MTBF doesn't that imply that half of these parts will still be working after 570 years of continuous use?
    Am I the only one who sees these predictions as absurd? What sort of curve "fitting" are they using for this reliability prediction?

    570 years ago (1437), the Byzantine empire still held Constantinople.