Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

get_model Takes more too long to initialise so the endpoint times out

See original GitHub issue

In the first get_model() call, the weight needs to be loaded and model initialized which is taking 10mins or so. The problem is that Sagemaker endpoint timeout after 60 seconds so the model never has time to initialize.

Would you have any suggestions on ways to address this?

Thanks

Issue Analytics

State:
Created 4 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

m4nuCcommented, May 16, 2019

Thanks for the input guys, I 've ended up using threading as well but with a less refined solution than @pm3310 suggest. I will try this out and confirm.

0reactions

pm3310commented, May 16, 2019

@m4nuC Perfect solution 😉

Top Results From Across the Web

Azure Machine Learning Python - Model class

With the Model class, you can package models for use with Docker and deploy them as a real-time endpoint that can be used...

Model — sagemaker 2.126.0 documentation

model_data_download_timeout (int) – The timeout value, in seconds, to download and extract model data from Amazon S3 to the individual inference instance ...

SageMaker — Boto3 Docs 1.26.34 documentation

Adds or overwrites one or more tags for the specified SageMaker resource. You can add tags to notebook instances, training jobs, hyperparameter tuning...

Delaying allocation when a node leaves | Elasticsearch Guide ...

For this reason, the default timeout is set to just one minute: even if shard relocation begins, cancelling recovery in favour of the...

sagemaker — AWS CLI 1.27.36 Command Reference

If you would like to suggest an improvement or fix for the AWS CLI, check out our contributing guide on GitHub. User Guide....