Thanks val, you are right, I am using sync API. It is fast enough for me. 

Thanks
Shawn

-----邮件原件-----
发件人: vkulichenko [mailto:[email protected]] 
发送时间: 2017年1月24日 3:39
收件人: [email protected]
主题: Re: 答复: ignite client memory issue

Shawn,

It looks like you had too many asynchronous operations executed at the same
time and therefore too many futures created in memory. Async approach
requires more accuracy, and if everything works for you with sync
operations, I would use them.

-Val



--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/ignite-client-memory-issue-tp
10174p10201.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Reply via email to