aws / aws/aws-step-functions-data-science-sdk-python
Add `deploy_instance_count` and `deploy_instance_type` to `TrainingPipeline`
- Dominant language
- Python
- Stars
- 299
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Description
Currently, [TrainingPipeline](https://github.com/aws/aws-step-functions-data-science-sdk-python/blob/b45b282592041d3c355f7cef492798bc3bf5415a/src/stepfunctions/template/pipeline/train.py#L95) 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.
Contributor guide
Research direction
Start with src/stepfunctions/template/pipeline/train.py, especially the TrainingPipeline definition linked in the issue. Trace how the current instance type and count are applied to training and deployment, then determine the configuration points for separate deploy values. Done means TrainingPipeline accepts deploy_instance_count and deploy_instance_type and uses them independently from the training settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud, machine-learning
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100