Dedicated queue version
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- backend, distributed-systems
Research direction
The issue describes a proposed Python queue server and benchmark runner, including webhook handling, persistent queuing, polling, subprocess execution, and update delivery, but names no files or tests. Start by reviewing the repository's current benchmark entry points and architecture; done would require an agreed design and implementation of both separated services.
Written by the indexing model from the issue text.
Description
Switch to Python for more maintainers.
Separate queue server and benchmark runner.
Queue server
Two parts: webhook server and persistent queue.
- webhook server accepts webhook request
- transforms certain ones into event on persistent queue
- from time to time checks for updates and potentially apply them¹
in order for the updates to be applied without losing requests, maybe put a load balancer or something like that in front of the webhook server
Benchmark runner
The benchmark runner should be a simple loop that executes the following steps
- check for and potentially apply update¹ for step 3.
- poll queue server. if event is available, execute step 3, else sleep then goto 1
- handle event using a subprocess that potentially got updated in step 1
- goto 1
¹E.g. we could use something like TUF / TUFup to check for and download updates
- Dominant language
- Rust
- Stars
- 4
- Forks
- 0
- Avg merge
- 5h 52m
- Merged PRs (30d)
- 4
Contributor guide
No contributing guide indexed for this repository
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.
More from scverse/benchmark
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
PR runs
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
PR runs Timeline
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Support OpenMeta
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Security OpenMeta
Difficulty 4/5 3-5 days Newbie friendliness 30/100
All issues in scverse/benchmark
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100