What it is, what to do about it, and why should you care.
Everyone expects their compute systems to generate the correct answer. When they don’t, it’s cause for alarm, because it’s not always clear how long the problem has persisted. Even worse, chips and systems are now so complex that it may require a unique sequence of operations to trigger a silent data error, and they may show up only occasionally, and maybe only after months or years of use in the field. The first challenge is to identify the problem, and then figure out what to do about it. Noam Brousard, vice president of solutions engineering at proteanTecs, talks with Semiconductor Engineering about the various causes of silent data corruption, why they’re so problematic, how they can manifest over time, and how to minimize the damage they can cause.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
Leave a Reply