Kukushkin [mailto:kukushkinale...@gmail.com]
*Sent:* Thursday, September 7, 2017 11:45 PM
*To:* user@ignite.apache.org
*Cc:* d...@ignite.apache.org
*Subject:* Re: Massive commit sizes for processes with local Ignite Grid
servers
Raymond,
So you see 3 "extra" GB that your server app ta
}
>>
>> };
>>
>>
>>
>> After running both servers the commit size peaked at 4Gb for both
>> processes (with ~430Mb actual allocated memory) which is s significant
>> improvement, though still seems higher than might be expec
>
>
>
> *From:* Dmitry Pavlov [mailto:dpavlov@gmail.com]
> *Sent:* Thursday, September 7, 2017 10:22 PM
> *To:* user@ignite.apache.org; d...@ignite.apache.org
> *Subject:* Re: Massive commit sizes for processes with local Ignite Grid
> servers
>
>
>
> Hi Raymon
Thanks,
Raymond.
*From:* Dmitry Pavlov [mailto:dpavlov@gmail.com]
*Sent:* Thursday, September 7, 2017 10:22 PM
*To:* user@ignite.apache.org; d...@ignite.apache.org
*Subject:* Re: Massive commit sizes for processes with local Ignite Grid
servers
Hi Raymond,
Total memory usage
Hi Raymond,
Total memory usage since 2.0 version is determined as sum of heap size and
memory policies MaxSizes (overall segment sizes). If it is not configured
there is 80% of physical RAM is used for each node (before 2.2). In 2.2
this behaviour will be changed.
To run several nodes at one PC i
I tried an experiment where I ran only two instances of the server locally,
this is the result in the Task Manager:
*From:* Raymond Wilson [mailto:raymond_wil...@trimble.com]
*Sent:* Thursday, September 7, 2017 9:21 PM
*To:* user@ignite.apache.org; 'd...@ignite.apache.org'
*Subject:* Massive