For each connection, on node side will be created its own datastreamer. I think it makes sense to try pooling for data load, but you will need to measure everything, since the pool size depends on the lot of things
вт, 14 апр. 2020 г. в 07:31, narges saleh <snarges...@gmail.com>: > Yes, Evgenii. > > On Mon, Apr 13, 2020 at 10:06 PM Evgenii Zhuravlev < > e.zhuravlev...@gmail.com> wrote: > >> Hi, >> >> Do you use STREAMING MODE for thin JDBC driver? >> >> Evgenii >> >> пн, 13 апр. 2020 г. в 19:33, narges saleh <snarges...@gmail.com>: >> >>> Thanks Alex. I will study the links you provided. >>> >>> I read somewhere that jdbc datasource is available via Ignite JDBC, >>> (which should provide connection pooling). >>> >>> On Mon, Apr 13, 2020 at 12:31 PM akorensh <alexanderko...@gmail.com> >>> wrote: >>> >>>> Hi, >>>> At this point you need to implement connection pooling yourself. >>>> Use >>>> >>>> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/ClientConnectorConfiguration.html#setThreadPoolSize-int- >>>> to specify number of threads Ignite creates to service connection >>>> requests. >>>> >>>> Each new connection will be handled by a separate thread inside >>>> Ignite(maxed out a threadPoolSize - as described above) >>>> >>>> ClientConnectorConfiguration is set inside IgniteConfiguration: >>>> >>>> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/IgniteConfiguration.html#setClientConnectorConfiguration-org.apache.ignite.configuration.ClientConnectorConfiguration- >>>> >>>> More info: >>>> >>>> https://www.gridgain.com/docs/latest/developers-guide/SQL/JDBC/jdbc-driver#cluster-configuration >>>> >>>> Thanks, Alex >>>> >>>> >>>> >>>> -- >>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >>>> >>>
