Code-Dependent and Architecture-Dependent Reliability Behaviors
Open accessThe DOI matches its Crossref record; 6 of the 6 references it cites were found in a registry or an index.
Abstract
The increased need for computing capabilities and higher efficiency have stimulated industries to make available in the market novel architectures with increased complexity. The variety of codes that need to be executed combined with the complexity of novel architectures introduces challenges in the reliability evaluation of computing systems and applications. This paper compares the reliability behaviors of six different architectures (an Intel co-processor, three NVIDIA GPUs, an AMD APU, an embedded ARM) executing eight different codes. To support our evaluation, we present and discuss experimental beam data that covers a total of more than 352,000 years of natural exposure and fault-injection analysis based on a total of more than 120,000 injections. We first quantify both the Silent Data Corruptions and the Detected Unrecoverable Errors rates. Then, we qualify observed errors considering the difference between the corrupted and expected values as well as the portion of the output that has been corrupted. From these analyses, we identify the reliability characteristics which are related to the underlying hardware and the intrinsic behaviors of the executed code. Finally, we discuss the implications of the device- and code-dependent reliability behaviors for approximate computing. We analyze the benefits, in term of reduced error rate, of a relaxed output correctness.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
You Only Look Once: Unified, Real-Time Object Detection
Redmon, J., Divvala, S., Girshick, R., & Farhadi, A. (2016) · 2016 IEEE Conference on Computer Vision and Pattern Recognition (CVPR) · doi:10.1109/cvpr.2016.91 · Cited by 53,803
Radiation-induced soft errors in advanced semiconductor technologies
Baumann, R. C. (2005) · IEEE Transactions on Device and Materials Reliability · doi:10.1109/tdmr.2005.853449 · Cited by 1,549
DEPENDABLE COMPUTING AND FAULT TOLERANCE : CONCEPTS AND TERMINOLOGY
Laprie, J.-C. (2005) · Twenty-Fifth International Symposium on Fault-Tolerant Computing, 1995, ' Highlights from Twenty-Five Years'. · doi:10.1109/ftcsh.1995.532603 · Cited by 460 · cited 1×
“Various sources of errors could undermine the system reliability, including environmental perturbations, software errors, and process, temperature, or voltage variations [1], [2].”
BackgroundSASSIFI: An architecture-level fault injection tool for GPU application resilience evaluation
Hari, S. K. S., Tsai, T., Stephenson, M., Keckler, S. W., & Emer, J. (2017) · 2017 IEEE International Symposium on Performance Analysis of Systems and Software (ISPASS) · doi:10.1109/ispass.2017.7975296 · Cited by 181
GPU-Qin: A methodology for evaluating the error resilience of GPGPU applications
Fang, B., Pattabiraman, K., Ripeanu, M., & Gurumurthi, S. (2014) · 2014 IEEE International Symposium on Performance Analysis of Systems and Software (ISPASS) · doi:10.1109/ispass.2014.6844486 · Cited by 142
Understanding Error Propagation in GPGPU Applications
Li, G., Pattabiraman, K., Cher, C.-Y., & Bose, P. (2016) · SC16: International Conference for High Performance Computing, Networking, Storage and Analysis · doi:10.1109/sc.2016.20 · Cited by 89 · cited 2×
“Additionally, a single corrupted thread could feed thousands of future parallel threads with erroneous data, leading to multiple output errors [18].”
Background
Cited by
Rech, P. (2024) · IEEE Transactions on Nuclear Science · doi:10.1109/tns.2024.3349956 · Cited by 75
“The comparison of beam data in GPUs, FPGAs, and CPUs executing different algorithms highlights that DUEs have a strong component that is independent of the executed code and is, then, related just to the hardware [127].”
BackgroundSelf-citationDemystifying the System Vulnerability Stack: Transient Fault Effects Across the Layers
Papadimitriou, G., & Gizopoulos, D. (2021) · 2021 ACM/IEEE 48th Annual International Symposium on Computer Architecture (ISCA) · doi:10.1109/isca52012.2021.00075 · Cited by 74
Increasing the Efficiency and Efficacy of Selective-Hardening for Parallel Applications
Oliveira, D., Navaux, P., & Rech, P. (2019) · 2019 IEEE International Symposium on Defect and Fault Tolerance in VLSI and Nanotechnology Systems (DFT) · doi:10.1109/dft.2019.8875300 · Cited by 5
“Unfortunately, besides offering a plethora of advantages, accelerators have been shown to have a higher error rate than traditional computing devices [1], [2].”
BackgroundSelf-citation
Metadata
- Authors
- Fratin, V., Oliveira, D., Lunardi, C., Santos, F., Rodrigues, G., & Rech, P.
- Venue
- 2018 48th Annual IEEE/IFIP International Conference on Dependable Systems and Networks (DSN)
- Publisher
- IEEE
- Published
- 2018-06
- Pages
- 13-26
- OpenAlex
- W2884175902
- Cited by
- 43
- References
- 6
- FWCI
- 9.65
- Type
- conference paper
- Language
- en
- Open access
- green
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Code-Dependent and Architecture-Dependent Reliability Behaviors. https://app.cochat.ai/papers/10.1109/dsn.2018.00015
- The paper
- Fratin, V., Oliveira, D., Lunardi, C., Santos, F., Rodrigues, G., & Rech, P. (2018). Code-Dependent and Architecture-Dependent Reliability Behaviors. 2018 48th Annual IEEE/IFIP International Conference on Dependable Systems and Networks (DSN). https://doi.org/10.1109/dsn.2018.00015
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.