1 Answer
- Newest
- Most votes
- Most comments
0
- The cold-start time you’re experiencing with your SageMaker endpoint is likely due to the time it takes to download and load the model when an instance is spun up. There isn’t a setting that persists the image/model in SageMaker.
- Asynchronous inference in SageMaker allows you to queue incoming requests and process them asynchronously. It’s useful for workloads with large payload sizes, long processing times, and near real-time latency requirements. It’s also cost-efficient as you can scale down your instances to zero when there are no requests to process.
- While it’s possible to deploy a Docker image in Amazon ECS, the process would be quite different from deploying it in SageMaker. You would need to handle aspects like load balancing, auto-scaling, and secure model data storage yourself.
- To reduce the time it takes for your endpoint to scale up in response to a request, you might want to look into defining a scaling policy that scales up from zero for new requests. However, the scaling up time might still be significant due to the reasons mentioned above.
Relevant content
asked a year ago
- AWS OFFICIALUpdated 2 years ago
