Regarding RPC bench

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

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

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.