jgreenemi/Parris

Introduce `around-cost` termination method.

Open

#1 opened on Jan 2, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (320 stars) (22 forks)batch import
good first issuehelp wanted

Description

Do some maths in the lambda-function.py file based on the instance type in use to determine what the time-limit should be set to, so that the user can set a max dollar value that they are willing to pay for the training session.

Contributor guide

Tech stack
pythonaws
Domain
machine learningcloudbackend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Python basicsAWS Lambda knowledgeUnderstanding of instance pricing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
The issue asks to modify `src/lambda function.py` around line 135 to add cost based termination logic. First, examine the existing code to understand how instance types are determined and where time limits are set. Then, research AWS instance pricing (e.g., on demand per hour) and calculate a time limit based on a user defined max dollar amount. Consider edge cases like spot instances or different regions. The implementation should accept a max cost parameter and compute the allowed duration. No linked PRs or comments exist; the maintainer should clarify if they prefer a specific formula or if the cost should be passed as an environment variable.