Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create comprehensive benchmarks #1285

Closed
dfawley opened this issue Jun 6, 2017 · 4 comments
Closed

Create comprehensive benchmarks #1285

dfawley opened this issue Jun 6, 2017 · 4 comments
Labels
P3 Type: Performance Performance improvements (CPU, network, memory, etc)

Comments

@dfawley
Copy link
Member

dfawley commented Jun 6, 2017

From #1043: Add a collection of benchmarks to measure our performance for different types of workloads under various network conditions (high and low bandwidth and latency). Performance metrics will include throughput, QPS, and tail latency (as well as localized metrics like allocations, syscalls, and CPU usage).

@dfawley dfawley added P1 Type: Performance Performance improvements (CPU, network, memory, etc) labels Jun 6, 2017
@dfawley dfawley self-assigned this Jun 6, 2017
@ZhouyihaiDing ZhouyihaiDing self-assigned this Jun 7, 2017
@dfawley dfawley removed their assignment Jun 23, 2017
@dfawley dfawley added P2 and removed P1 labels Aug 24, 2017
@menghanl menghanl added P3 and removed P2 labels Dec 14, 2017
@dfawley
Copy link
Member Author

dfawley commented Mar 1, 2018

Remaining work: a benchmark that sends messages in an unconstrained fashion (as opposed to ping-pong)

@MakMukhi
Copy link
Contributor

#1952 Solves all of this except for options to control network conditions.

@dfawley
Copy link
Member Author

dfawley commented Jun 13, 2018

Actually, we have the network parameters in there already. But we're still missing unconstrained-streaming-RPC benchmarks.

@dfawley
Copy link
Member Author

dfawley commented Jun 5, 2019

This is now implemented in the benchmarks.

@dfawley dfawley closed this as completed Jun 5, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Dec 2, 2019
@lock lock bot unassigned canguler Dec 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P3 Type: Performance Performance improvements (CPU, network, memory, etc)
Projects
None yet
Development

No branches or pull requests

5 participants