TY - JOUR
T1 - Architecture-Aware Approximate Computing
AU - Karakoy, Mustafa
AU - Kislal, Orhan
AU - Tang, Xulong
AU - Kandemir, Mahmut Taylan
AU - Arunachalam, Meenakshi
N1 - Funding Information:
We thank Murali Annavaram for shepherding our paper. We thank the anonymous reviewers for their feedback. This research is supported in part by NSF grants #1526750, #1763681, #1439057, #1439021, #1629129, #1409095, #1626251, #1629915, and a grant from Intel.
Publisher Copyright:
© 2019 Copyright is held by the owner/author(s).
PY - 2019/12/17
Y1 - 2019/12/17
N2 - Observing that many application programs from different domains can live with less-Than-perfect accuracy, existing techniques try to trade off program output accuracy with performance-energy savings. While these works provide point solutions, they leave three critical questions regarding approximate computing unanswered: (i) what is the maximum potential of skipping (i.e., not performing) data accesses under a given inaccuracy bound?; (ii) can we identify the data accesses to drop randomly, or is being architecture aware critical?; and (iii) do two executions that skip the same number of data accesses always result in the same output quality (error)? This paper first provides answers to these questions using ten multithreaded workloads, and then presents a program slicing-based approach that identifies the set of data accesses to drop. Results indicate 8.8% performance improvement and 13.7% energy saving are possible when we set the error bound to 2%, and the corresponding improvements jump to 15% and 25%, respectively, when the error bound is raised to 4%.
AB - Observing that many application programs from different domains can live with less-Than-perfect accuracy, existing techniques try to trade off program output accuracy with performance-energy savings. While these works provide point solutions, they leave three critical questions regarding approximate computing unanswered: (i) what is the maximum potential of skipping (i.e., not performing) data accesses under a given inaccuracy bound?; (ii) can we identify the data accesses to drop randomly, or is being architecture aware critical?; and (iii) do two executions that skip the same number of data accesses always result in the same output quality (error)? This paper first provides answers to these questions using ten multithreaded workloads, and then presents a program slicing-based approach that identifies the set of data accesses to drop. Results indicate 8.8% performance improvement and 13.7% energy saving are possible when we set the error bound to 2%, and the corresponding improvements jump to 15% and 25%, respectively, when the error bound is raised to 4%.
UR - http://www.scopus.com/inward/record.url?scp=85086499029&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=85086499029&partnerID=8YFLogxK
U2 - 10.1145/3309697.3331508
DO - 10.1145/3309697.3331508
M3 - Article
AN - SCOPUS:85086499029
SN - 0163-5999
VL - 47
SP - 23
EP - 24
JO - Performance Evaluation Review
JF - Performance Evaluation Review
IS - 1
ER -