spcl / spcl/serverless-benchmarks
Persistent URL allocation for 120.uploader
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 199
- Forks
- 105
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the benchmark 120.uploader runs by pulling data from external servers: Wikipedia, GitHub, and PyTorch. Not only does this introduce the risk of failure (Wikipedia keeps changing its policies), but it also introduces an additional variability factor - we're not only measuring the I/O performance of Lambda and storage, but also of the external server.
We could introduce a new variant of the benchmark that serves the data from a self-deployed HTTP server on a VM with strong I/O performance or a scalable cloud storage.
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 locating the 120.uploader benchmark and tracing how it currently retrieves data from Wikipedia, GitHub, and PyTorch. Define a controlled data-serving variant using a self-deployed HTTP server or scalable cloud storage, with completion meaning the benchmark no longer depends on external servers or their I/O variability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100