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

Better request/response benchmark #112

Open
pipermerriam opened this issue Jun 1, 2019 · 0 comments
Open

Better request/response benchmark #112

pipermerriam opened this issue Jun 1, 2019 · 0 comments

Comments

@pipermerriam
Copy link
Member

What was wrong?

the request/response benchmarks would be better if the reporting occurred on the Driver side and it reported round trip, or if it reported on both sides of the request/response side so we knew both the 1/2 and full round trip times (and ideally the computed metric of the response time).

How can it be fixed?

Adjust how the driver and workers operate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant