Query

[Gagan Juneja <ga...@gmail.com>]

Hi All,

While exploring the code I found that we are using Thrift implementation of
TThreadPoolServer with default 30 threads. As per my experience, this
Thrift server implementation is very resource intensive though it gives
good performance is some scenarios. Are we establishing peer to peer
connections?



Regards,
Gagan

Re: Query

[Marlon Pierce <ma...@iu.edu>]

Thanks, Gagan, the link below provides some good comparisons.

Marlon

On 6/1/14 4:29 PM, Gagan Juneja wrote:
> Yes this is configurable. A very nice comparison on all available thirft
> Java servers can be found at [1].
>
> I am not very much sure about the number of concurrent users our system
> supposed to cater But the only thing is TThreadPoolServer uses one thread
> per user request and keep it tied to that request until the request is
> closed. So let's say if at a time there are 1000 users
> then TThreadPoolServer need 1000 threads from the pool otherwise will be
> waiting for the threads to get released.
>
> TThreadedSelectorServer is always a safe choice with some latency and
> throughput hit.
>
>
> Regards,
> Gagan
>
>
> [1] https://github.com/m1ch1/mapkeeper/wiki/Thrift-Java-Servers-Compared
>
>
>
>
> On Sun, Jun 1, 2014 at 8:15 PM, Chathuri Wimalasena <ka...@gmail.com>
> wrote:
>
>> Hi Gagan,
>>
>> Number of threads is configurable from airavata-server.properties.
>>
>>
>> On Sun, Jun 1, 2014 at 9:47 AM, Saminda Wijeratne <sa...@gmail.com>
>> wrote:
>>
>>> Thanks Gagan. We used have the TSimpleServer, but we switched to
>>> TThreadPoolServer because we needed concurrent access to the server. Please
>>> do feel free to analyze the usage more and provide more feedback and
>>> suggestions based on your expertise in thrift. We'll greatly benefit if
>>> there are architectural changes we can detect beforehand.
>>>
>>> Thanks,
>>> Saminda
>>>
>>>
>>> On Sun, Jun 1, 2014 at 6:34 AM, Gagan Juneja <ga...@gmail.com>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> While exploring the code I found that we are using Thrift implementation
>>>> of TThreadPoolServer with default 30 threads. As per my experience, this
>>>> Thrift server implementation is very resource intensive though it gives
>>>> good performance is some scenarios. Are we establishing peer to peer
>>>> connections?
>>>>
>>>>
>>>>
>>>> Regards,
>>>> Gagan
>>>>
>>>>

Re: Query

[Gagan Juneja <ga...@gmail.com>]

Yes this is configurable. A very nice comparison on all available thirft
Java servers can be found at [1].

I am not very much sure about the number of concurrent users our system
supposed to cater But the only thing is TThreadPoolServer uses one thread
per user request and keep it tied to that request until the request is
closed. So let's say if at a time there are 1000 users
then TThreadPoolServer need 1000 threads from the pool otherwise will be
waiting for the threads to get released.

TThreadedSelectorServer is always a safe choice with some latency and
throughput hit.


Regards,
Gagan


[1] https://github.com/m1ch1/mapkeeper/wiki/Thrift-Java-Servers-Compared




On Sun, Jun 1, 2014 at 8:15 PM, Chathuri Wimalasena <ka...@gmail.com>
wrote:

> Hi Gagan,
>
> Number of threads is configurable from airavata-server.properties.
>
>
> On Sun, Jun 1, 2014 at 9:47 AM, Saminda Wijeratne <sa...@gmail.com>
> wrote:
>
>> Thanks Gagan. We used have the TSimpleServer, but we switched to
>> TThreadPoolServer because we needed concurrent access to the server. Please
>> do feel free to analyze the usage more and provide more feedback and
>> suggestions based on your expertise in thrift. We'll greatly benefit if
>> there are architectural changes we can detect beforehand.
>>
>> Thanks,
>> Saminda
>>
>>
>> On Sun, Jun 1, 2014 at 6:34 AM, Gagan Juneja <ga...@gmail.com>
>> wrote:
>>
>>> Hi All,
>>>
>>> While exploring the code I found that we are using Thrift implementation
>>> of TThreadPoolServer with default 30 threads. As per my experience, this
>>> Thrift server implementation is very resource intensive though it gives
>>> good performance is some scenarios. Are we establishing peer to peer
>>> connections?
>>>
>>>
>>>
>>> Regards,
>>> Gagan
>>>
>>>
>>
>

Re: Query

[Chathuri Wimalasena <ka...@gmail.com>]

Hi Gagan,

Number of threads is configurable from airavata-server.properties.


On Sun, Jun 1, 2014 at 9:47 AM, Saminda Wijeratne <sa...@gmail.com>
wrote:

> Thanks Gagan. We used have the TSimpleServer, but we switched to
> TThreadPoolServer because we needed concurrent access to the server. Please
> do feel free to analyze the usage more and provide more feedback and
> suggestions based on your expertise in thrift. We'll greatly benefit if
> there are architectural changes we can detect beforehand.
>
> Thanks,
> Saminda
>
>
> On Sun, Jun 1, 2014 at 6:34 AM, Gagan Juneja <ga...@gmail.com>
> wrote:
>
>> Hi All,
>>
>> While exploring the code I found that we are using Thrift implementation
>> of TThreadPoolServer with default 30 threads. As per my experience, this
>> Thrift server implementation is very resource intensive though it gives
>> good performance is some scenarios. Are we establishing peer to peer
>> connections?
>>
>>
>>
>> Regards,
>> Gagan
>>
>>
>

Re: Query

[Saminda Wijeratne <sa...@gmail.com>]

Thanks Gagan. We used have the TSimpleServer, but we switched to
TThreadPoolServer because we needed concurrent access to the server. Please
do feel free to analyze the usage more and provide more feedback and
suggestions based on your expertise in thrift. We'll greatly benefit if
there are architectural changes we can detect beforehand.

Thanks,
Saminda


On Sun, Jun 1, 2014 at 6:34 AM, Gagan Juneja <ga...@gmail.com>
wrote:

> Hi All,
>
> While exploring the code I found that we are using Thrift implementation
> of TThreadPoolServer with default 30 threads. As per my experience, this
> Thrift server implementation is very resource intensive though it gives
> good performance is some scenarios. Are we establishing peer to peer
> connections?
>
>
>
> Regards,
> Gagan
>
>