From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] pineview atom
Date: Thu, 18 Feb 2010 13:39:06 -0500 [thread overview]
Message-ID: <c1ae15d2c80dc5c8dbbdc28ee274f29d@coraid.com> (raw)
In-Reply-To: <4B7D8650.6030409@maht0x0r.net>
> of non-ECC memory, so nice terminal, bad server
>
>
> "the probability of having at least one bit error in 4 gigabyes of
> memory at sea level on planet Earth in 72 hours is over 95%."
>
>
> http://lambda-diode.com/opinion/ecc-memory
while i agree in general that ecc is a good idea, i can't
subscribe to predictions that seem so far from real-world
experience.
i have been running a amd64 machine as a cpu server
for 2 years. it uses standard ddr2 memory. i have not
seen any unexplained crashes or reboots during this time.
at work, i have been running 5 un-ecc'd machines for
3 years. also no unexplained crahses or reboots.
how could this be if i would expect 240 + 1825 bit errors?
- erik
next prev parent reply other threads:[~2010-02-18 18:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 16:56 erik quanstrom
2010-02-18 18:26 ` matt
2010-02-18 18:31 ` ron minnich
2010-02-18 18:43 ` Patrick Kelly
2010-02-18 20:04 ` David Leimbach
2010-02-18 18:39 ` erik quanstrom [this message]
2010-02-18 20:46 ` ron minnich
2010-02-18 21:03 ` erik quanstrom
2010-02-18 21:14 ` Dave Eckhardt
2010-02-18 22:38 ` erik quanstrom
2010-02-18 23:08 ` roger peppe
2010-02-18 23:12 ` Adrian Tritschler
2010-02-18 23:27 ` ron minnich
2010-02-19 21:59 ` Dave Eckhardt
2010-02-20 22:17 ` erik quanstrom
2010-02-21 19:46 ` Dave Eckhardt
2010-03-05 10:01 ` hugh
2010-03-05 17:32 ` Dave Eckhardt
2010-02-18 18:43 ` Corey Thomasson
2010-03-08 17:57 ` Albert Skye
2010-03-08 19:06 ` erik quanstrom
2010-03-08 19:47 ` Jonas Amoson
2010-03-08 20:11 ` erik quanstrom
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=c1ae15d2c80dc5c8dbbdc28ee274f29d@coraid.com \
--to=quanstro@labs.coraid.com \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).