简体   繁体   English

用于模型托管的 AWS Sagemaker 与 ECS

[英]AWS Sagemaker vs ECS for model hosting

I have pretrained model artifacts stored in S3 buckets.我在 S3 存储桶中存储了预训练的模型工件。 I want to create a service that loads this model and uses it for inference.我想创建一个加载此模型并将其用于推理的服务。

I am working in AWS ecosystem and confused between using ECS vs Sagemaker for model deployment?我在 AWS 生态系统中工作,对使用 ECS 还是 Sagemaker 进行模型部署感到困惑? What are some pros/cons for choosing one over other?选择一个而不是另一个有哪些优点/缺点?

SageMaker has a higher price mark but it is taking a lot of the heavy lifting of deploying a machine learning model, such as wiring the pieces (load balancer, gunicorn, CloudWatch, Auto-Scaling...) and it is easier to automate the processes such as A/B testing. SageMaker 的价格更高,但它承担了部署机器学习模型的大量繁重工作,例如连接各个部分(负载均衡器、gunicorn、CloudWatch、Auto-Scaling...),并且更容易实现自动化A/B 测试等流程。

If you have a strong team of DevOps that have nothing more important to do, you can build a flow that will be cheaper than the SageMaker option.如果您拥有一支强大的 DevOps 团队而没有更重要的事情要做,那么您可以构建一个比 SageMaker 选项更便宜的流程。 ECS and EKS are doing at the same time a lot of work to make it very easy for you to automate the machine learning model deployments. ECS 和 EKS 同时做了很多工作,使您可以轻松实现机器学习模型部署的自动化。 However, they will always be more general purpose and SageMaker with its focus on machine learning will be easier for these use cases.但是,它们将始终具有更通用的用途,并且专注于机器学习的 SageMaker 将更容易用于这些用例。

The usual pattern of using the cloud is to use the managed services early on as you want to move fast and you don't really know where are your future problems.使用云的通常模式是尽早使用托管服务,因为您想要快速移动并且您不知道未来的问题在哪里。 Once the system is growing and you start feeling some pains here and there, you can decide to spend the time and improve that part of the system.一旦系统不断发展并且您开始在这里和那里感到一些痛苦,您就可以决定花时间改进系统的那部分。 Therefore, if you don't know the pros/cons, start with using the simpler options.因此,如果您不知道利弊,请从使用更简单的选项开始。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM