| Deutsch English Français Italiano |
|
<kooodjhvqc6b1eavj9rp4mkvna6np9e5mq@4ax.com> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!Xl.tags.giganews.com!local-3.nntp.ord.giganews.com!nntp.supernews.com!news.supernews.com.POSTED!not-for-mail NNTP-Posting-Date: Sat, 07 Sep 2024 14:35:12 +0000 From: john larkin <jlarkin_highland_tech> Newsgroups: sci.electronics.design Subject: Re: DRAM accommodations Date: Sat, 07 Sep 2024 07:35:11 -0700 Message-ID: <kooodjhvqc6b1eavj9rp4mkvna6np9e5mq@4ax.com> References: <vbdcrs$gp01$1@dont-email.me> <vbflbe$tlhp$7@dont-email.me> <nnd$62817d9e$7d687883@ae30f02eb1959576> <vbhc0g$1bjbi$1@dont-email.me> User-Agent: ForteAgent/8.00.32.1272 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 30 X-Trace: sv3-LTG7ssWl1qFfRAyiV4I4T64okvoQrYHJnSrLZQt9LtZuDbZcWgOPJppOTa0Rc8PyRB+TUxfVsqCbm3B!zHfuzWPn04xYThciZEMBPn3z8Q1byxvqBa5Ne7Pe9rnchdHLF/seDdj4wrDVRhLWlwJoosUAgsN5!z1h1iQ== X-Complaints-To: www.supernews.com/docs/abuse.html X-DMCA-Complaints-To: www.supernews.com/docs/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 Bytes: 2444 On Sat, 7 Sep 2024 04:04:37 -0700, Don Y <blockedofcourse@foo.invalid> wrote: >On 9/7/2024 2:56 AM, albert@spenarnc.xs4all.nl wrote: >>> Back of the napkin figures suggest many errors are (silently!) encountered >>> in an 8-hour shift. For XIP implementations, it's mainly data that is at >>> risk (though that can also include control flow information from, e.g., >>> the pushdown stack). For implementations that load their application >>> into DRAM, then the code is suspect as well as the data! >>> >>> [Which is likely to cause more detectable/undetectable problems?] >> >> Running many day long computations for e.g. the euler project, >> involving giga byte memories, and require precise (not one off >> results), >> I have not encountered any wrong results caused by RAM failures. > >Do you KNOW that there haven't been any that your ECC *hasn't* silently >corrected for you? ECC is there so they can increase dram density. Increasing density and using multi levels per bit cell makes dram and flash cheaper and increases the raw error rate, and adding ecc bits makes it tolerably reliable, and that tradeoff is cost optimized. It seems to work pretty well. My PC here has 32Gbytes of dram and a terabyte of SSD, and seem fine. The combination runs Spice fast and the results work.