hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Rawson <ryano...@gmail.com>
Subject Re: HTTP transport?
Date Mon, 05 Oct 2009 20:57:22 GMT
That's good to know. I thought ka would help... but I was also talking about
the overhead of a header where the payload is smaller than the framing. Eg:
8 byte requests, excluding which rpc. This seems like we could be hurt since
the headers are potentially 5x the size of our payload/request params.

On Oct 5, 2009 4:54 PM, "Eric Sammer" <eric@lifeless.net> wrote:


Certainly keep alive will help in this case, if that's what you're
referring to. The server holds the socket for N seconds or M requests,
which ever comes first. What you're saving with KA is the connection
setup / tear down. If you have a lot of cases where the client makes a
single request and goes away, then KA hurts because the server holds the
connection for the KA timeout (N seconds). This *really* helps if you're
using TLS due to the additional connection setup overhead.

It's my opinion and experience that KA helps greatly in the case of many
exchanges between a small to medium number of clients and a server such
as RPC. The anti-example is an ad server or web beacon server, for instance.


Ryan Rawson wrote: > I have a question about these headers... will they
impact the ability to do > ...

Eric Sammer eric@lifless.net http://esammer.blogspot.com

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message