-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Optimize http_bench_json_ops example #16505
Conversation
Let’s publish polloi as a crate? |
Maybe when we use it somewhere apart from the example? It's just more code to compile if we add it to the workspace |
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.
It seems odd to have this one benchmark use polloi while the rest of the system uses tokio...
I don't think it is working. The last benchmark run on CI run gets 1 request per second.
|
…nto optimize_core_baseline
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.
Because this is an old PR I want to review again in detail if you want to land.
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.
@ry PTAL
// When a `TcpStream` resource is closed, all pending 'read' ops are | ||
// canceled, while 'write' ops are allowed to complete. Therefore only | ||
// 'read' futures are attached to this cancel handle. | ||
cancel: CancelHandle, |
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.
Why is this removed?
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.
Because cancellation is not used in the benchmark.
fn close(self: Rc<Self>) { | ||
self.cancel.cancel() | ||
} |
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.
Ditto
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
No description provided.