Cited by 10Cloud Computing and Resource ManagementRecommender Systems and TechniquesSoftware System Performance and Reliability

Migrating a Recommendation System to Cloud Using ML Workflow

Chahal, Dheeraj, Ojha, Ravi, Choudhury, Sharod Roy, Nambiar, Manoj·2020·Companion of the ACM/SPEC International Conference on Performance Engineering

Abstract

Inference is the production stage of machine learning workflow in which a trained model is used to infer or predict with real world data. A recommendation system improves customer experience by displaying most relevant items based on historical behavior of a customer. Machine learning models built for recommendation systems are deployed either on-premise or migrated to a cloud for inference in real time or batch. A recommendation system should be cost effective while honoring service level agreements (SLAs). In this work we discuss on-premise implementation of our recommendation system called iPrescribe. We show a methodology to migrate on-premise implementation of recommendation system to a cloud using ML workflow. We also present our study on performance of recommendation system model when deployed on different types of virtual instances.

Integrity signals

Registry

Crossref · 10.1145/3375555.3384423

Cites

7 of 7 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?

  • When using an ML deployment service such as SageMaker, the service may handle the deployment of serialized models.

    “When using an ML deployment service (e.g., SageMaker 7 ), the service may handle the deployment of serialized models [9].”
  • Another reported method of integration is to serialize the model and load it at runtime, possibly with an ML framework optimized for production.

    “Another reported method of integration is to serialize the model (e.g., into ONNXfoot_2 , HDF5, Joblib 4 ) and load it at runtime, possibly with an ML framework that is optimized for production [9,21,39,40].”
  • Serving-related challenges are some of the ones most often reported in the literature, usually from a performance perspective.

    “Serving-related challenges are some of the ones most often reported in the literature [5-7, 9, 11, 12, 16, 20, 28, 34, 44, 53, 54], usually from a performance perspective.”
  • Increasing hardware instances and network bandwidth both improve inference latencies.

    “The difficulty in achieving cost-effective and performant inference was also corroborated by [9], in which the authors observed that increasing hardware instances and network bandwidth both improve inference latencies.”
  • A static storage service such as AWS S3 may be used for model storage when models are downloaded by the target deployment environment.

    “When models are downloaded by the target deployment environment, a static storage service such as AWS S3 27 may be used for model storage [9,29].”

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Chahal, D., Ojha, R., Choudhury, S. R., & Nambiar, M.
Affiliations
TCS Research, MUMBAI, India
Venue
Companion of the ACM/SPEC International Conference on Performance Engineering
Publisher
ACM
Published
2020-04-20
Pages
1-4
OpenAlex
W3021354258
Cited by
10
References
7
Citations by year
2025: 1 · 2023: 1 · 2022: 4 · 2021: 1 · 2020: 3
FWCI
1.71
Type
conference paper
Language
en
Open access
closed
Locations
ACM/SPEC International Conference on Performance Engineering (ICPE) (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Information Systems › Cloud Computing and Resource Management
  • Physical Sciences › Computer Science › Information Systems › Recommender Systems and Techniques
  • Physical Sciences › Computer Science › Computer Networks and Communications › Software System Performance and Reliability
Keywords
recommender systems, cloud migration, machine learning workflow, inference, on-premise deployment, virtual machine instances, performance evaluation, service level agreements, cost-effectiveness

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