Cited by 23Cloud Computing and Resource ManagementIoT and Edge/Fog ComputingEnergy Efficiency in Computing

Missing the Forest for the Trees: End-to-End AI Application Performance in Edge Data Centers

Richins, Daniel, Doshi, Dharmisha, Blackmore, Matthew, Thulaseedharan Nair, Aswathy, Pathapati, Neha, Patel, Ankit, Daguman, Brainard, Dobrijalowski, Daniel +4 more·2020·2020 IEEE International Symposium on High Performance Computer Architecture (HPCA)

Abstract

Artificial intelligence and machine learning are experiencing widespread adoption in the industry, academia, and even public consciousness. This has been driven by the rapid advances in the applications and accuracy of AI through increasingly complex algorithms and models; this, in turn, has spurred research into developing specialized hardware AI accelerators. The rapid pace of the advances makes it easy to miss the forest for the trees: they are often developed and evaluated in a vacuum without considering the full application environment in which they must eventually operate. In this paper, we deploy and characterize Face Recognition, an AI-centric edge video analytics application built using open source and widely adopted infrastructure and ML tools. We evaluate its holistic, end-to-end behavior in a production-size edge data center and reveal the "AI tax" for all the processing that is involved. Even though the application is built around state-of-the-art AI and ML algorithms, it relies heavily on pre-and post-processing code which must be executed on a general-purpose CPU. As AI-centric applications start to reap the acceleration promised by so many accelerators, we find they impose stresses on the underlying software infrastructure and the data center's capabilities: storage and network bandwidth become major bottlenecks with increasing AI acceleration. By not having to serve a wide variety of applications, we show that a purpose-built edge data center can be designed to accommodate the stresses of accelerated AI at 15% lower TCO than one derived from homogeneous servers and infrastructure. We also discuss how our conclusions generalize beyond Face Recognition as many AI-centric applications at the edge rely upon the same underlying software and hardware infrastructure.

Integrity signals

Registry

Crossref · 10.1109/hpca47549.2020.00049

Cites

26 of 26 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • In a system utilizing publish/subscribe messaging services, 33% of application latency is a result of internal communication frameworks.

    “In a system utilizing publish/subscribe messaging services, [44] observed that 33% of application latency is a result of internal communication frameworks, and by experimentation, found that the messaging system becomes congested when faced with an eightfold increase in inference performance.”
  • The messaging system becomes congested when faced with an eightfold increase in inference performance.

    “by experimentation, found that the messaging system becomes congested when faced with an eightfold increase in inference performance.”
  • Data pre- and post-processing code in streaming ML systems could soon become another performance bottleneck.

    “[44] warns that the data pre-and post-processing code in streaming ML systems could soon become another performance bottleneck.”
  • Increasing the number of broker node instances used in the messaging system clears up the congestion issue.

    “The authors found that a solution to the problem could be to increase the number of broker node instances used in the messaging system, which clears up the congestion issue.”
  • Docker is by far the most frequently reported solution for packaging ML models in containers.

    “Docker 17 is by far the most frequently reported solution [12,16,20,26,28,40,44].”

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Richins, D., Doshi, D., Blackmore, M., Thulaseedharan Nair, A., Pathapati, N., Patel, A., Daguman, B., Dobrijalowski, D., Illikkal, R., Long, K., Zimmerman, D., & Janapa Reddi, V.
Affiliations
  • The University of Texas at Austin (US)
  • Intel (United States) (US)
Venue
2020 IEEE International Symposium on High Performance Computer Architecture (HPCA)
Publisher
IEEE
Published
2020-02
Pages
515-528
ISSN
1530-0897 (ISSN-L)
OpenAlex
W3016892718
Cited by
23
References
26
Citations by year
2026: 2 · 2024: 6 · 2023: 2 · 2022: 3 · 2021: 7 · 2020: 2 · 2019: 1
FWCI
2.66
Type
conference paper
Language
en
Open access
closed
Locations
IEEE International Symposium on High-Performance Computer Architecture (HPCA) (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Information Systems › Cloud Computing and Resource Management
  • Physical Sciences › Computer Science › Computer Networks and Communications › IoT and Edge/Fog Computing
  • Physical Sciences › Computer Science › Hardware and Architecture › Energy Efficiency in Computing
Keywords
AI acceleration, face recognition, storage bottlenecks, network bandwidth, total cost of ownership

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