Hi, As I see from code of CacheAbstractJdbcStore it will try to use range query if possible.
see: CacheAbstractJdbcStore#loadCacheRange As you are using SQL Server make sure that SQLServerDialect was set to your store, please provide config generated by Web Console. Or just set a break point and trace down to CacheAbstractJdbcStore#loadCacheRange and see what it is doing actually. Or attach a reproducer here (generate project + sample SQL dump of your data, do not forget to replace sensitive data by random stuff). On Mon, Sep 17, 2018 at 3:56 PM wt <[email protected]> wrote: > Hi > > I have a project that is generated by the web console (2.5) and it is > loading an integrated db (SQL Server) table that has 4.5 million rows. When > running the load cache it is loading 1-3 records per second which is > unacceptable. Looking at the documentation i see examples of the overridden > load cache mechanism which makes me think that the default loading > mechanism > in this project is not optimal for bulk loads. If i run a query on the jdbc > db driver it is returning 100k of rows per second. > > Looking for advice here as i want to maintain the strategy of not needing > to > write load code but obviously want something that wont take forever to > load. > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > -- Alexey Kuznetsov
