-
Notifications
You must be signed in to change notification settings - Fork 824
[10384] Adding Zero Copy feature to the Latency performance tests #1742
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
Conversation
da5d556
to
b2d87e4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know we have discussed it already, and we all though it was a good solution, but how fair is to discard the echo bounce time in the measurements? Isn't that part of the 'consequences' of using, for example, the loan API? If having to wait for a loan makes our overall latency worse, should we assume it on the measurements?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…res due to resource outage.
adaf353
to
04d04d4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the not dynamic case, the CSV and STDOUT tables show and incorrect size for bytes larger than what the user requested (68 instead of 64). I have not tested with dynamic data though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
This PR should be merged after PR #1706, #1730 and #1705.