Open collin opened 10 years ago
:+1: most awesome issue/comment/read in a while
Any idea where the extra Expect: 100-continue
was coming from?
FYI, for benchmarking tools like ab
, httperf
, siege
, and wrk
are probably all better choices. wrk
is presently my personal favorite.
From curl
, is that what you mean? Or does reel support this and I'm
getting two of these?
Thanks for the suggestions, I'll have to check out wrk
.
On Tue, Oct 15, 2013 at 12:41 PM, Tony Arcieri notifications@github.comwrote:
Any idea where the extra Expect: 100-continue was coming from?
FYI, for benchmarking tools like ab, httperf, siege, and wrk are probably all better choices. wrk is presently my personal favorite.
— Reply to this email directly or view it on GitHubhttps://github.com/celluloid/reel/issues/111#issuecomment-26355970 .
So the difference here is that node's HTTP server is handling it internally and Reel is not?
Yes, the behavior for node is defined here: http://nodejs.org/api/http.html#http_event_checkcontinue
On Tue, Oct 15, 2013 at 12:48 PM, Tony Arcieri notifications@github.comwrote:
So the difference here is that node's HTTP server is handling it internally and Reel is not?
— Reply to this email directly or view it on GitHubhttps://github.com/celluloid/reel/issues/111#issuecomment-26356545 .
This is very interesting. Thank you very much for brining this to my attention!
@collin I'm assessing this for 0.7.0
and am wondering if you've progressed with this on your end at all? Any private code out there resolving this?
No, I don't have anything for this.
On Thu, Jan 22, 2015 at 4:41 PM, digitalextremist notifications@github.com wrote:
@collin https://github.com/collin I'm assessing this for 0.7.0 and am wondering if you've progressed with this on your end at all? Any private code out there resolving this?
— Reply to this email directly or view it on GitHub https://github.com/celluloid/reel/issues/111#issuecomment-71114195.
Low priority, but I was having a heart attack for a moment when doing some benchmarks vs node and learned something new about HTTP and curl.
Curl against ruby server:
Curl against node server:
At first I was thinking, "Oh no! node is so much faster than ruby. What have I been doing wrong with my life."
Then I noticed the extra
HTTP/1.1 100 Continue
I added that extra header to my request handler and SWEET GLORY! Ruby really is my friend.
Not sure if this is in-scope for reel, but even some sort of log message pointing me in the right direction would have prevented much un-warranted soul searching and hair pulling. :D