.net thin client taking time to establish connection to server node

classic Classic list List threaded Threaded
13 messages Options
siva siva
Reply | Threaded
Open this post in threaded view
|

.net thin client taking time to establish connection to server node

This post was updated on .
Hi,

We are using .net thinclient  and  one serever(.net) .For less number of
connections,its establishing connection to the server in milliseconds ,but
as the number of connections increasing(concurrently), establishing
connection between thin client and server taking in seconds even some times
taking upto 1 minute.So, is there any tuning to set or need to increase the
server nodes?


 client = Ignition.StartClient(new IgniteClientConfiguration
            {
                Endpoints = endpoints,
                SocketTimeout = TimeSpan.FromSeconds(30)

            });


Thanks
siva



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
ptupitsyn ptupitsyn
Reply | Threaded
Open this post in threaded view
|

Re: .net thin client taking time to establish connection to server node

Hi, try increasing ClientConnectorConfiguration.ThreadPoolSize on server nodes

On Sun, Sep 15, 2019 at 11:10 AM siva <[hidden email]> wrote:
Hi,

We are using *.net thinclient * and *one serever(.net)*.For less number of
connections,its establishing connection to the server in milliseconds ,but
as the number of connections increasing(concurrently), establishing
connection between thin client and server taking in seconds even some times
taking upto 1 minute.So, is there any tuning to set or need to increase the
server nodes?






Thanks
siva



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
siva siva
Reply | Threaded
Open this post in threaded view
|

Re: .net thin client taking time to establish connection to server node

This post was updated on .
Hi,


I have increased threadpool size to 20 threads  in xml file as bellow since
we have 16 cores. But still result is same, taking time to establish
connection.

<property name="clientConnectorConfiguration">
      <bean class="org.apache.ignite.configuration.ClientConnectorConfiguration">
        <property name="threadPoolSize" value="20"/>
      </bean>
    </property>




Results
<http://apache-ignite-users.70518.x6.nabble.com/file/t1379/Screenshot_1.png



Thanks
siva



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
ptupitsyn ptupitsyn
Reply | Threaded
Open this post in threaded view
|

Re: .net thin client taking time to establish connection to server node

How many connections do you have? Can you share a reproducer please?

On Tue, Sep 17, 2019 at 12:06 PM siva <[hidden email]> wrote:
Hi,


I have increased threadpool size to 20 threads  in xml file as bellow since
we have 16 cores. But still result is same, taking time to establish
connection.







Results
<http://apache-ignite-users.70518.x6.nabble.com/file/t1379/Screenshot_1.png>



Thanks
siva



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
siva siva
Reply | Threaded
Open this post in threaded view
|

Re: .net thin client taking time to establish connection to server node

This post was updated on .
Hi,

How many connections do you have?

requests will come from external applications around 30k in duration  of 30
min or more.Each request ,  opened connection  not closing  up to 1/2/3 min
since within the same request it can be multiple calls to ignite.

<http://apache-ignite-users.70518.x6.nabble.com/file/t1379/Screenshot_3.png

i have attached sample result

Thanks
siva



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
ptupitsyn ptupitsyn
Reply | Threaded
Open this post in threaded view
|

Re: .net thin client taking time to establish connection to server node

So 30000 simultaneous connections to one server node, right?

On Tue, Sep 17, 2019 at 12:58 PM siva <[hidden email]> wrote:
Hi,

*How many connections do you have?*

requests will come from external applications around 30k in duration  of 30
min or more.Each request ,  opened connection  not closing  up to 1/2/3 min
since within the same request it can be multiple calls to ignite.

<http://apache-ignite-users.70518.x6.nabble.com/file/t1379/Screenshot_3.png>

i have attached sample result

Thanks
siva



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
ptupitsyn ptupitsyn
Reply | Threaded
Open this post in threaded view
|

Re: .net thin client taking time to establish connection to server node

I did some testing and did not find any inherent limitation for thin client connection count.
So it is likely that your server is simply overloaded with work. 

- Check CPU and RAM usage on the server
- Check Java GC activity with jvisualvm or similar tool and try system tuning: https://apacheignite.readme.io/docs/jvm-and-system-tuning
- Try increasing thread pool size further

On Tue, Sep 17, 2019 at 9:35 PM Pavel Tupitsyn <[hidden email]> wrote:
So 30000 simultaneous connections to one server node, right?

On Tue, Sep 17, 2019 at 12:58 PM siva <[hidden email]> wrote:
Hi,

*How many connections do you have?*

requests will come from external applications around 30k in duration  of 30
min or more.Each request ,  opened connection  not closing  up to 1/2/3 min
since within the same request it can be multiple calls to ignite.

<http://apache-ignite-users.70518.x6.nabble.com/file/t1379/Screenshot_3.png>

i have attached sample result

Thanks
siva



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
siva siva
Reply | Threaded
Open this post in threaded view
|

Re: .net thin client taking time to establish connection to server node

Hi,

*Check CPU and RAM usage on the server*
Cpu utilization upto 20% max
RAM More than half memory free


*Try increasing thread pool size further*
Increased to 24 threads


Found issue but not sure,like if any exception in executing query ,in that
time period other clients try to connect ,in that case its taking long
time.Is that limitation?



Thanks
siva



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
ptupitsyn ptupitsyn
Reply | Threaded
Open this post in threaded view
|

Re: .net thin client taking time to establish connection to server node

Exceptions should not cause a slowdown. Can you please provide a minimal reproducer?

On Thu, Sep 19, 2019 at 10:41 AM siva <[hidden email]> wrote:
Hi,

*Check CPU and RAM usage on the server*
Cpu utilization upto 20% max
RAM More than half memory free


*Try increasing thread pool size further*
Increased to 24 threads


Found issue but not sure,like if any exception in executing query ,in that
time period other clients try to connect ,in that case its taking long
time.Is that limitation?



Thanks
siva



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
siva siva
Reply | Threaded
Open this post in threaded view
|

Re: .net thin client taking time to establish connection to server node

Hi Pavel,

*Can you please provide a minimal reproducer?*

for reproducing,i have  tried  in local ,its taking minimal time only,but
from actual application(staging environment (cloud))  its taking more time
to establish the connection .


I have taken 5 minute  duration in staging env ,to create client connection
total 325 request arrived ,out of these 9 requests taken from 300 ms to 3
sec.

I have attached the screen shots

<http://apache-ignite-users.70518.x6.nabble.com/file/t1379/Screenshot_1.png>

<http://apache-ignite-users.70518.x6.nabble.com/file/t1379/Screenshot_2.png>



Thanks
siva








--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
ptupitsyn ptupitsyn
Reply | Threaded
Open this post in threaded view
|

Re: .net thin client taking time to establish connection to server node

Maybe something else is affecting request time in staging?
Do you make requests from your local machine to staging environment?
How fast is the connection between thin client and server?

On Mon, Sep 30, 2019 at 1:28 PM siva <[hidden email]> wrote:
Hi Pavel,

*Can you please provide a minimal reproducer?*

for reproducing,i have  tried  in local ,its taking minimal time only,but
from actual application(staging environment (cloud))  its taking more time
to establish the connection .


I have taken 5 minute  duration in staging env ,to create client connection
total 325 request arrived ,out of these 9 requests taken from 300 ms to 3
sec.

I have attached the screen shots

<http://apache-ignite-users.70518.x6.nabble.com/file/t1379/Screenshot_1.png>

<http://apache-ignite-users.70518.x6.nabble.com/file/t1379/Screenshot_2.png>



Thanks
siva








--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
siva siva
Reply | Threaded
Open this post in threaded view
|

Re: .net thin client taking time to establish connection to server node

This post was updated on .
Hi Pavel,


Maybe something else is affecting request time in staging?
chances of others services trying to connect (from front end requests)

Do you make requests from your local machine to staging environment?
yes,i have made a request to the staging environment ignite server from
local machine console app to test.

How fast is the connection between thin client and server?


from local machine to local ignite server its taking microseconds and
milliseconds upto 10ms max

but from local machine to  staging ignite server(cloud) its taking more
time.
i have attached the screen shot


Code


This github code describes similer to the client applications trying  to the
ignite server

https://github.com/cvakarna/ignitethinclient-reproducer/tree/master/IgniteConnectionTest
<https://github.com/cvakarna/ignitethinclient-reproducer/tree/master/IgniteConnectionTest

This github link similer to the server code
https://github.com/cvakarna/ignitereproducer/tree/master/IgniteReproducerServer
<https://github.com/cvakarna/ignitereproducer/tree/master/IgniteReproducerServer



<http://apache-ignite-users.70518.x6.nabble.com/file/t1379/Screenshot_3.png





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
ptupitsyn ptupitsyn
Reply | Threaded
Open this post in threaded view
|

Re: .net thin client taking time to establish connection to server node

Tried to run the reproducer and got `Cache doesn't exist: 6e7b08b5-3bfd-4026-b322-c4a34ffkafd7_Forms` exception.

On Tue, Oct 1, 2019 at 3:16 PM siva <[hidden email]> wrote:
Hi Pavel,


*Maybe something else is affecting request time in staging?*
chances of others services trying to connect (from front end requests)

*Do you make requests from your local machine to staging environment?*
yes,i have made a request to the staging environment ignite server from
local machine console app to test.

*How fast is the connection between thin client and server?
*

from local machine to local ignite server its taking microseconds and
milliseconds upto 10ms max

but from local machine to  staging ignite server(cloud) its taking more
time.
i have attached the screen shot


*Code
*

This github code describes similer to the client applications trying  to the
ignite server

https://github.com/cvakarna/ignitethinclient-reproducer/tree/master/IgniteConnectionTest
<https://github.com/cvakarna/ignitethinclient-reproducer/tree/master/IgniteConnectionTest

This github link similer to the server code
https://github.com/cvakarna/ignitereproducer/tree/master/IgniteReproducerServer
<https://github.com/cvakarna/ignitereproducer/tree/master/IgniteReproducerServer



<http://apache-ignite-users.70518.x6.nabble.com/file/t1379/Screenshot_3.png>





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/