jgreenemi/Parris

Introduce `around-cost` termination method.

Open

#1 建立於 2018年1月2日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)Python (320 star) (22 fork)batch import
good first issuehelp wanted

描述

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.

貢獻者指南

技術棧
pythonaws
領域
machine learningcloudbackend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Python basicsAWS Lambda knowledgeUnderstanding of instance pricing
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
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.
Introduce `around-cost` termination method. · jgreenemi/Parris#1 | Good First Issue