thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Slifka <rsli...@sfu.ca>
Subject Re: Thrift client connection pooling?
Date Fri, 25 Sep 2009 01:51:50 GMT
Thanks Michael, just checking in to be sure I was going down an avenue that made sense.

I've seen links to Commons Pool - I'll check it out too.

Rob


----- Original Message -----
From: "Michael Greene" <michael.greene@gmail.com>
To: thrift-user@incubator.apache.org
Sent: Thursday, September 24, 2009 3:52:52 PM GMT -08:00 US/Canada Pacific
Subject: Re: Thrift client connection pooling?

This is what I've seen some other libraries that consume Thrift do as well.
 In Java, the Apache Commons Object Pool works pretty well -- I use a
hand-written pool that's relatively similar in C#.
Michael

On Thu, Sep 24, 2009 at 5:38 PM, Jake Luciani <jakers@gmail.com> wrote:

> I often use thread specific storage. 1 connection maintained per thread.
>
> Sent from my iPhone
>
>
> On Sep 24, 2009, at 5:56 PM, Rob Slifka <rslifka@sfu.ca> wrote:
>
>  Hi everyone,
>>
>> Just curious if/how anyone is doing client side connection pooling?
>>
>> For simplicity's sake, we're opening and closing connections on demand.
>> The trick is that under load you run out of native sockets as a flurry of
>> requests result in closed connections in TIME_WAIT.
>>
>> Any thoughts on this?
>>
>> Rob
>>
>>

Mime
View raw message