Ganesh,
Thin driver uses one of the nodes as a gateway, so once you add second node,
half of updates will have to make two network hops instead of one, so
slowdown is expected. Although, it should not get worse further when you add
third, fourth and so on node.
The best option for this case would
Hi ,
Following is the java code as requested.
sql = INSERT INTO Mon1_0 ( T_ID,kpi4,kpi5,id,kpi2,kpi3,kpi1)
VALUES(?,?,?,?,?,?,?)
preparedStatement = con.prepareStatement(sql.
toString(),
ResultSet.
*TYPE_FORWARD_ONLY*
What is the Java source code? Most of the people have difficulties to write
proper Java JDBC code for bulk inserts (even for normal databases). It requires
some thinking on threading, buffers and of course selecting the right
methodology to insert etc
> On 24. Jan 2018, at 08:20, Ganesh Sarde
Hi ,
We are using ignite JDBC thin driver to store 1 million records in a table
on ignite cache. To insert 1 Million records on single node it take 60 sec,
whereas on cluster of 2 nodes it takes 5 min and time grows exponentially
as number of nodes are increased.
attached ignite log file where ti
