spcl / spcl/serverless-benchmarks
Cost estimations
Open
Nobody has claimed this yet.
aws
azure
gcp
good first issue
- Dominant language
- Python
- Stars
- 199
- Forks
- 105
- PR merge metrics
- No merged PRs in 30d
Description
Currently, our perf-cost experiment does not attempt to provide any cost estimations. We should provide this functionality, hardcode cloud costs per supported regions (or query them, if there's an API for it):
- Function duration and memory costs
- Function invocation costs
- State transitions for workflows
- Estimate storage accesses
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the perf-cost experiment and how supported regions and cloud-provider data are represented. Determine how to obtain or maintain pricing for duration, memory, invocations, workflow state transitions, and storage accesses. Done means the experiment reports cost estimates for each requested category across supported regions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100