Public-Environmental-Data-Partners / Public-Environmental-Data-Partners/EJAM-API
optimize deployment
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 1
- Forks
- 1
- Avg merge
- 38m
- Merged PRs (30d)
- 1
Description
Currently, EJAM-API is deployed on Google Cloud Run and from there it receives requests for reports, generates them, and serves them. It does so rather slowly.
Configuration:
8GB memory, 4vCPU
minimum number of instances = 0
instance-based billing ("Full CPU for the entire lifetime of each instance.")
"start-up boost"
I just don't know enough about deployment options to know what would be better/best.
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
No files or tests are named. Start by reviewing the Google Cloud Run deployment configuration listed in the issue and compare available deployment options for the report-serving API. Done means selecting and documenting a faster, justified configuration, then validating report request performance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud
- Domain
- cloud, devops
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100