I mean startup of the client application. Best Regards, Igor
On Mon, May 16, 2016 at 7:18 PM, Igor Sapego <[email protected]> wrote: > Arthi, > > Why do you create one client node per user request? Can you create > a node on application start and then just use this node instance when > you need to make a request? > > > Best Regards, > Igor > > On Mon, May 16, 2016 at 6:41 PM, arthi <[email protected] > > wrote: > >> Hi Igor, >> >> this is my usecase - I use the ignite data grid to store my business data >> in >> memory. My client application needs to run SQL queries on this data. Every >> client request in the application will be translated to multiple SQL >> queries. The application needs to support 400-500 concurrent users. >> My client application is written in C++. >> >> My grid can grow to have terabytes of data across 30-40 server nodes. >> >> The SLA for the one request/response is < 30 sec. My SQL queries come back >> faster, its the ignite client joining time I would want to reduce. I >> create >> one client node per user request and that instance is used to execute the >> multiple SQL queries to get the response. >> >> what is the best that is possible in terms of client join time? Can it be >> <1-2 secs? My servers are Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz with >> 256GB RAM and 40 cores, the n/w between the nodes is high speed too. >> >> Thanks, >> Arthi >> >> >> >> -- >> View this message in context: >> http://apache-ignite-users.70518.x6.nabble.com/Get-client-node-instance-tp4897p4960.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > >
