Regarding RPC bench
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go
- Domain
- backend-api-design, performance
Research direction
Review the existing RPC benchmark setup to confirm how connections are created for each call. Define realistic scenarios covering multiplexed RPCs over a shared connection and fixed-QPS workloads, then compare the resulting measurements with the current benchmark. Done means these scenarios are implemented and their results are reproducible.
Written by the indexing model from the issue text.
Description
Hi,
It is interesting to compare these schemes and thanks for the result. I just want to point out the scenario specified here seems not be representative RPC use case -- you initiated a new connection for each rpc. I understood that this was probably because you want to do sorta apple-to-apple comparison between RPC and http1.1. But multiplexing rpcs on a single connection is a very important advantage of rpc framework compared http1.1.
Plus, it would be helpful if you introduce more realistic scenarios such as fixed QPS benchmark.
I saw your guys have pending debate on rpc or rest. The above (multiplexing and fixed QPS benchmark) will show the advantage of rpc.
- Dominant language
- Go
- Stars
- 87
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
Similar issues
-
☢️ Bug v3
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area/import-export area/projects concern/ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
go-vikunja/vikunja#4455 · 1 comment ·
Maintainers usually reply within 2 days
-
Dependabot PRs no longer merge automaticallyPossibly taken @dwisiswant0 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
projectdiscovery/urlfinder#160 ·
Maintainers usually reply within 1 day
-
database
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
chnm/legal-modernism#450 ·
Maintainers usually reply within 1 day
-
tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day