Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upnet: Try to turn on HTTP pooling. #6026
Conversation
|
It looks correct to me. Here's possible reasons it's not reused:
Turning on If they're One situation needs to handled manually in this PR: if the pooled connection has been killed or timed out by the server, it will still be in the Pool and given out when another connection is requested. I imagine handling the error case when passing I haven't thought of a good way to do that myself in hyper yet. |
|
I'm not keen on the huge block in which the connector is exclusively locked. Is there a way to minimize that? |
|
@jdm I tried to get it as small as I reasonably could, but I could try to do better. Note that apparently if we do another hyperup, we won't need the lock at all. |
|
Yea, that will be in 0.5, no longer taking a |
|
I minimized the lock and added retrying in the case @seanmonstar requested. r? @jdm |
|
-S-awaiting-review +S-awaiting-answer Review status: all files reviewed, 1 unresolved discussion, all commit checks successful.
components/net/http_loader.rs, line 139 [r1] (raw file): Comments from the review on Reviewable.io |
|
Addressed comment. r? @jdm |
|
@bors-servo: r+ Review status: all files reviewed, all discussions resolved, some commit checks pending.
Comments from the review on Reviewable.io |
|
|
But I don't see any actual pooling going on in Wireshark. What am I doing wrong? r? @jdm r? @seanmonstar <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/6026) <!-- Reviewable:end -->
|
|
|
|
|
|
I found eventually that in cases where the response was chunked, the stream wouldn't be reused. Responses with |
|
@pcwalton ping. This one is getting quite old. |
net: Try to turn on HTTP pooling. rebased and fixed up #6026 (Can't compile some of the native dependencies on my current machine, so I'll have to rely on travis?). Also, better if viewed with [w=1](https://github.com/servo/servo/compare/servo:master...seanmonstar:pool?expand=1&w=1). <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/6948) <!-- Reviewable:end -->
net: Try to turn on HTTP pooling. rebased and fixed up #6026 (Can't compile some of the native dependencies on my current machine, so I'll have to rely on travis?). Also, better if viewed with [w=1](https://github.com/servo/servo/compare/servo:master...seanmonstar:pool?expand=1&w=1). <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/6948) <!-- Reviewable:end -->
pcwalton commentedMay 12, 2015
But I don't see any actual pooling going on in Wireshark. What am I
doing wrong?
r? @jdm
r? @seanmonstar