Thanks val, you are right, I am using sync API. It is fast enough for me.
Thanks
Shawn
-邮件原件-
发件人: vkulichenko [mailto:valentin.kuliche...@gmail.com]
发送时间: 2017年1月24日 3:39
收件人: user@ignite.apache.org
主题: Re: 答复: ignite client memory issue
Shawn,
It looks like you had too many asynchro
ondition and
> worthy further investigate.
>
> Thanks
> Shawn
>
> 发件人: Shawn Du [mailto:shawn...@neulion.com.cn]
> 发送时间: 2017年1月22日 17:36
> 收件人: user@ignite.apache.org
> 主题: RE: ignite client memory issue
>
>
cn]
发送时间: 2017年1月22日 13:52
收件人: user@ignite.apache.org
主题: Re: ignite client memory issue
Hi,
I assume this document for ignite server. In my case, I set ignite work at
client mode.
Now I increase the Max Heap Size and my application is running, I will monitor
the memory usage.
For my view,
Magda [mailto:dma...@apache.org]
发送时间: 2017年1月22日 13:38
收件人: user@ignite.apache.org
主题: Re: ignite client memory issue
Also keep in mind that every Ignite node requires at least ~ 300 MB for its
internal purposes. This capacity planning page might be useful as well for you:
https
收件人: user@ignite.apache.org
> 主题: Re: ignite client memory issue
>
> Hi Shawn,
>
> What is the maximum size of the heap?
>
> I don’t think the cache configurations can be a reason of the OOM. As a side
> note, there is no reason to keep the configurations at all. Once a
Hi Shawn,
What is the maximum size of the heap?
I don’t think the cache configurations can be a reason of the OOM. As a side
note, there is no reason to keep the configurations at all. Once a cache is
started with a configuration you can either keep a single reference to it and
reuse by multi
