Hi, *-when restarted node, It took 6 hrs to activate again, * If you activated cluster on startup, before data loading, then after restart, cluster is active.
*-queries are very slower, * it depends. What SQL queries do you have? JOIN, AGG? *-out of memory issue when loading data. * Show your CacheConfiguration * -huge size for data.* If you enable QueryEnity for SQL support, Ignite consumes much more memory. *Best Regards, Andrey Dolmatov* вт, 9 июл. 2019 г. в 16:10, shahidv <[email protected]>: > Hi, > > We are looking for new database technologies because of some performance > issues in existing. > So we tried ignite with 1 node cluster (28gb ram), loaded 90 million > records > to the cache. > But we faced several issues like, > -when restarted node, It took 6 hrs to activate again, > -queries are very slower, > -out of memory issue when loading data. > -huge size for data. > > We are still learning stage to Ignite and it may be some configuration > issues. > We have currently large volume of data and processing heavy aggregations. > > Anyone please tell me Ignite will be a solution for performance and what is > the issue with my current setup. Following is my config. file, > default-config.xml > < > http://apache-ignite-users.70518.x6.nabble.com/file/t2499/default-config.xml> > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
