Hi Lucky, Also you can try to remove indices from configuration and create them dynamically via "CREATE INDEX" sql query after load finished.
On Thu, Oct 12, 2017 at 10:36 AM, Lucky <wanxing...@163.com> wrote: > afedotov > Thanks a lot ! > > It took 25 seconds with cache.putAll performance. this is better than > "insert into..."; > I have send the configuration what you need. > Please see the attachment. > > > Thanks. > Lucky > > > At 2017-10-11 18:19:18, "afedotov" <alexander.fedot...@gmail.com> wrote: > >Hi, > > > >Did you have a chance to compare the results with cache.put performance? > > > >You mentioned that you set writeBehind to true, so do you have a cache store > >configured? > >What is the INSERT rate for the underlying DB in this case? > > > >Did you enable persistent store option? > >What is CPU and memory utilization? > >Do you observe any GC issues? > > > >Please share Ignite and GC logs. > > > >Kind regards, > >Alex > > > > > > > >-- > >Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > > > > 【网易自营|30天无忧退货】仅售同款价1/4！MUJI制造商“2017秋冬舒适家居拖鞋系列”限时仅34.9元>> > <http://you.163.com/item/detail?id=1165011&from=web_gg_mail_jiaobiao_9> > > -- Best regards, Andrey V. Mashenkov
