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
tion
>
> {
>
> Name = "defaultPolicy",
>
> MaxSize = 4L * 1024 * 1024 * 1025 // 4 GB
>
> }
>
> }
>
>
>
> чт, 7 сент. 2017 г. в 12:44, Raymond Wilson :
>
> I tried an experiment where I ran only two instances of the server
&
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
> d...@ignite.apache.org>
> *Subject:* Massive commit sizes for processes with local Ignite Grid
> servers
>
>
>
> I’m running a set of four server applications on a local system to
> simulate a cluster.
>
>
>
> Each of the servers has the following memory conf
:* Massive commit sizes for processes with local Ignite Grid servers
I’m running a set of four server applications on a local system to simulate
a cluster.
Each of the servers has the following memory configurations set:
public override void ConfigureRaptorGrid(IgniteConfigu
I’m running a set of four server applications on a local system to simulate
a cluster.
Each of the servers has the following memory configurations set:
public override void ConfigureRaptorGrid(IgniteConfiguration cfg)
{
cfg.JvmInitialMemoryMb = 512; // Set to min
