From: Paulo Marques <pmarques@grupopie.com>
To: John Richard Moser <nigelenki@comcast.net>
Cc: David Vrabel <dvrabel@cantab.net>, linux-kernel@vger.kernel.org
Subject: Re: Lifetime of flash memory
Date: Tue, 21 Mar 2006 18:37:08 +0000 [thread overview]
Message-ID: <442047D4.5010208@grupopie.com> (raw)
In-Reply-To: <442037D2.7060109@comcast.net>
John Richard Moser wrote:
> David Vrabel wrote:
>
>>John Richard Moser wrote:
>>
>>>The question I have is, is this really significant? I have heard quoted
>>>that flash memory typically handles something like 3x10^18 writes;
>>
>>That's like, uh, 13 orders of magnitudes out...
>
> Yeah I did more searching, it looks like that was a mass overstatement.
> There was one company that did claim to have developed flash memory
> with that size (I think it was 3.8x10^18) but it looks like typical
> drives are 1.0x10^6 with an on-chip wear-leveling algorithm.
That is still high. Modern flash drives will do 100.000 writes for SLC
(single-level cells) or 10.000 writes for MLC (multi-level cells) [1].
> Assuming
> the drive is like 256 megs with 64k blocks, that's still 129 years at
> one write per second.
This is also assuming _perfect_ wear leveling. There are real world
drives with crappy (or even buggy) wear levelling. I've seen CF cards
die with much less writting than this.
Even then, with just 10.000 writes, this is already reduced to 1.29
years, assuming 64kb/sec average writting.
If you take into consideration that you can actually write 6Mbytes/sec
on a modern CF card, you can fry a 256Mb card in just 5 days, if you
write continuously.
--
Paulo Marques - www.grupopie.com
Pointy-Haired Boss: I don't see anything that could stand in our way.
Dilbert: Sanity? Reality? The laws of physics?
[1] check out: http://www.kingston.com/products/DMTechGuide.pdf
next prev parent reply other threads:[~2006-03-21 18:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 17:01 Lifetime of flash memory John Richard Moser
2006-03-21 17:14 ` David Vrabel
2006-03-21 17:28 ` John Richard Moser
2006-03-21 18:37 ` Paulo Marques [this message]
2006-03-21 18:00 ` hackmiester / Hunter Fuller
2006-03-21 18:20 ` Joshua Kugler
2006-03-21 18:40 ` John Richard Moser
2006-03-23 3:46 ` Kalin KOZHUHAROV
-- strict thread matches above, loose matches on Subject: below --
2006-03-23 7:49 linux
2006-03-26 13:55 ` Artem B. Bityutskiy
2006-03-26 16:21 ` linux
2006-03-26 16:36 ` Artem B. Bityutskiy
2006-03-27 16:18 ` Lennart Sorensen
2006-03-27 17:44 ` linux-os (Dick Johnson)
2006-03-27 18:01 ` Lennart Sorensen
2006-03-28 4:28 ` Sergei Organov
2006-03-28 6:41 ` Magnus Damm
2006-03-28 8:58 ` Sergei Organov
2006-03-28 12:55 ` linux-os (Dick Johnson)
2006-03-28 13:27 ` Sergei Organov
2006-03-28 13:35 ` Sergei Organov
2006-03-29 1:01 ` linux
2006-03-29 4:33 ` Sergei Organov
2006-03-29 15:56 ` linux
2006-03-30 6:33 ` Sergei Organov
2006-03-30 11:23 ` linux
2006-03-30 12:18 ` Sergei Organov
2006-03-28 0:21 ` Bill Davidsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=442047D4.5010208@grupopie.com \
--to=pmarques@grupopie.com \
--cc=dvrabel@cantab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nigelenki@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox