aws-step-functions-data-science-sdk-python
aws-step-functions-data-science-sdk-python copied to clipboard
Add `deploy_instance_count` and `deploy_instance_type` to `TrainingPipeline`
trafficstars
Currently, TrainingPipeline uses the same instance type and count for both train and deploy.
Different instance types and counts are desirable to address the different profiles for each workload.
Thanks for the feedback @cfregly. The use case of having different instance types and counts for training and the endpoint is a valid one. We will look into this.
Cool. we ended up hacking it here: https://github.com/data-science-on-aws/workshop/blob/a7c5603/10_pipeline/01_Create_Pipeline_Train_and_Deploy_Reviews_BERT_TensorFlow.ipynb
(search for TrainingPipelineWithDifferentDeployInstanceType)